Skip to content

Commit

Permalink
update 'git rebase' documentation
Browse files Browse the repository at this point in the history
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 <szeder@ira.uka.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
  • Loading branch information
SZEDER Gábor authored and Junio C Hamano committed Mar 11, 2008
1 parent 5447aac commit 702088a
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 4 deletions.
3 changes: 1 addition & 2 deletions Documentation/git-rebase.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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, <branch> will be the current branch.
Upon completion, <branch> will be the current branch.

INTERACTIVE MODE
----------------
Expand Down
3 changes: 1 addition & 2 deletions git-rebase.sh
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +18,7 @@ original <branch> and remove the .dotest working files, use the command
git rebase --abort instead.
Note that if <branch> 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
Expand Down

0 comments on commit 702088a

Please sign in to comment.