From 702088afc680afef231d4a24bb5890f1d96a2cc9 Mon Sep 17 00:00:00 2001 From: =?utf8?q?SZEDER=20G=C3=A1bor?= Date: Mon, 10 Mar 2008 15:38:33 +0100 Subject: [PATCH] update 'git rebase' documentation MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Being in the project's top directory when starting or continuing a rebase is not necessary since 533b703 (Allow whole-tree operations to be started from a subdirectory, 2007-01-12). Signed-off-by: SZEDER Gábor Signed-off-by: Junio C Hamano --- Documentation/git-rebase.txt | 3 +-- git-rebase.sh | 3 +-- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt index 4b1030474..e0412e086 100644 --- a/Documentation/git-rebase.txt +++ b/Documentation/git-rebase.txt @@ -262,8 +262,7 @@ hook if one exists. You can use this hook to do sanity checks and reject the rebase if it isn't appropriate. Please see the template pre-rebase hook script for an example. -You must be in the top directory of your project to start (or continue) -a rebase. Upon completion, will be the current branch. +Upon completion, will be the current branch. INTERACTIVE MODE ---------------- diff --git a/git-rebase.sh b/git-rebase.sh index 452c5e7e0..ff66af3ba 100755 --- a/git-rebase.sh +++ b/git-rebase.sh @@ -18,8 +18,7 @@ original and remove the .dotest working files, use the command git rebase --abort instead. Note that if is not specified on the command line, the -currently checked out branch is used. You must be in the top -directory of your project to start (or continue) a rebase. +currently checked out branch is used. Example: git-rebase master~1 topic -- 2.30.2