git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] update 'git rebase' documentation

From
SZEDER Gábor <szeder@ira.uka.de>
Date
Mar 10, 2008, 14:38 UTC
Message-ID
<1205159913-19925-1-git-send-email-szeder@ira.uka.de>

Being in the project's top directory when starting or continuing a rebase is not necessary since 533b70390e540de4e0faed4823ee561c8368e5ec

Signed-off-by: SZEDER Gábor <szeder@ira.uka.de>
---
 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 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
 
-- 
1.5.4.4.481.g5075
Message 1 of 1 in “update 'git rebase' documentation”
  1. update 'git rebase' documentationSZEDER Gábor, Mar 10, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.