summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLibravatar Johannes Schindelin <johannes.schindelin@gmx.de>2018-10-10 01:53:56 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2018-10-11 17:13:37 +0900
commitb8c0b2100bbcbbfe324962b0f15c92207d945895 (patch)
tree8edaf07a8be7901eca2f731f20b1a2b245fbc2b7
parentrebase -i: move rebase--helper modes to rebase--interactive (diff)
downloadtgif-b8c0b2100bbcbbfe324962b0f15c92207d945895.tar.xz
rebase -i: clarify what happens on a failed `exec`
We had not documented previously what happens when an `exec` command in an interactive rebase fails. Now we do. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/git-rebase.txt3
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt
index 091eb53faa..d9771bd25b 100644
--- a/Documentation/git-rebase.txt
+++ b/Documentation/git-rebase.txt
@@ -420,7 +420,8 @@ idea unless you know what you are doing (see BUGS below).
--exec <cmd>::
Append "exec <cmd>" after each line creating a commit in the
final history. <cmd> will be interpreted as one or more shell
- commands.
+ commands. Any command that fails will interrupt the rebase,
+ with exit code 1.
+
You may execute several commands by either using one instance of `--exec`
with several commands: