Skip to content

Commit

Permalink
rebase -i: clarify what happens on a failed exec
Browse files Browse the repository at this point in the history
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>
  • Loading branch information
dscho authored and gitster committed Oct 11, 2018
1 parent 34b4731 commit b8c0b21
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion Documentation/git-rebase.txt
Expand Up @@ -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:
Expand Down

0 comments on commit b8c0b21

Please sign in to comment.