summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSZEDER Gábor <szeder@ira.uka.de>2008-03-10 14:38:33 (GMT)
committerJunio C Hamano <gitster@pobox.com>2008-03-11 00:38:03 (GMT)
commit702088afc680afef231d4a24bb5890f1d96a2cc9 (patch)
tree2e3050d5a33c43e9f710da855005d1a3e584f05e
parent5447aac755e5cfb948c627762b4665801811b026 (diff)
downloadgit-702088afc680afef231d4a24bb5890f1d96a2cc9.zip
git-702088afc680afef231d4a24bb5890f1d96a2cc9.tar.gz
git-702088afc680afef231d4a24bb5890f1d96a2cc9.tar.bz2
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>
-rw-r--r--Documentation/git-rebase.txt3
-rwxr-xr-xgit-rebase.sh3
2 files changed, 2 insertions, 4 deletions
diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt
index 4b10304..e0412e0 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, <branch> will be the current branch.
+Upon completion, <branch> will be the current branch.
INTERACTIVE MODE
----------------
diff --git a/git-rebase.sh b/git-rebase.sh
index 452c5e7..ff66af3 100755
--- a/git-rebase.sh
+++ b/git-rebase.sh
@@ -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