summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2009-10-19 00:49:21 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2009-10-19 00:49:21 -0700
commite79999b1a285d4dcf1d84bc893c864516a390cfa (patch)
treecebc2524c6c0421e4590b2200802d3f64734075c /Documentation
parentformat_commit_message(): fix function signature (diff)
parentrebase -i: fix reword when using a terminal editor (diff)
downloadtgif-e79999b1a285d4dcf1d84bc893c864516a390cfa.tar.xz
Merge branch 'bg/rebase-reword'
* bg/rebase-reword: rebase -i: fix reword when using a terminal editor Teach 'rebase -i' the command "reword"
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/git-rebase.txt9
1 files changed, 6 insertions, 3 deletions
diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt
index 0aefc34d0d..33e0ef1f6d 100644
--- a/Documentation/git-rebase.txt
+++ b/Documentation/git-rebase.txt
@@ -368,14 +368,17 @@ By replacing the command "pick" with the command "edit", you can tell
the files and/or the commit message, amend the commit, and continue
rebasing.
+If you just want to edit the commit message for a commit, replace the
+command "pick" with the command "reword".
+
If you want to fold two or more commits into one, replace the command
"pick" with "squash" for the second and subsequent commit. If the
commits had different authors, it will attribute the squashed commit to
the author of the first commit.
-In both cases, or when a "pick" does not succeed (because of merge
-errors), the loop will stop to let you fix things, and you can continue
-the loop with `git rebase --continue`.
+'git-rebase' will stop when "pick" has been replaced with "edit" or
+when a command fails due to merge errors. When you are done editing
+and/or resolving conflicts you can continue with `git rebase --continue`.
For example, if you want to reorder the last 5 commits, such that what
was HEAD~4 becomes the new HEAD. To achieve that, you would call