update 'git rebase' documentation
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>
SZEDER Gábor committed
Mar 10, 2008 at 15:38 UTC
702088afc680afef231d4a24bb5890f1d96a2cc9
2 files changed
+2
-4
Documentation/git-rebase.txt
+1
-2
@@ -262,8 +262,7 @@ hook if one exists. You can use this hook to do sanity checks and
262
reject the rebase if it isn't appropriate. Please see the template
263
pre-rebase hook script for an example.
264
265
-You must be in the top directory of your project to start (or continue)
266
-a rebase. Upon completion, <branch> will be the current branch.
265
+Upon completion, <branch> will be the current branch.
266
267
INTERACTIVE MODE
268
----------------
git-rebase.sh
+1
-2
@@ -18,8 +18,7 @@ original <branch> and remove the .dotest working files, use the command
18
git rebase --abort instead.
19
20
Note that if <branch> is not specified on the command line, the
21
-currently checked out branch is used. You must be in the top
22
-directory of your project to start (or continue) a rebase.
21
+currently checked out branch is used.
22
23
Example: git-rebase master~1 topic
24