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>
Johannes Schindelin committed
Oct 10, 2018 at 01:53 UTC
b8c0b2100bbcbbfe324962b0f15c92207d945895
1 file changed
+2
-1
Documentation/git-rebase.txt
+2
-1
@@ -420,7 +420,8 @@ idea unless you know what you are doing (see BUGS below).
420
--exec <cmd>::
421
Append "exec <cmd>" after each line creating a commit in the
422
final history. <cmd> will be interpreted as one or more shell
423
- commands.
423
+ commands. Any command that fails will interrupt the rebase,
424
+ with exit code 1.
425
+
426
You may execute several commands by either using one instance of `--exec`
427
with several commands: