From: Johannes Schindelin Date: Wed, 10 Oct 2018 08:53:56 +0000 (-0700) Subject: rebase -i: clarify what happens on a failed `exec` X-Git-Tag: v2.20.0-rc0~84^2~1 X-Git-Url: https://git.lorimer.id.au/gitweb.git/diff_plain/b8c0b2100bbcbbfe324962b0f15c92207d945895?ds=inline;hp=--cc 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 Signed-off-by: Junio C Hamano --- b8c0b2100bbcbbfe324962b0f15c92207d945895 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 :: Append "exec " after each line creating a commit in the final history. 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: