From: Johannes Schindelin via GitGitGadget Date: Fri, 12 Oct 2018 13:14:24 GMT Subject: [PATCH v3 1/2] rebase -i: clarify what happens on a failed `exec` Message-ID: <92512a82d27b57dedf9dc9423dfac2efcb229031.1539350061.git.gitgitgadget@gmail.com> In-Reply-To: From: Johannes Schindelin We had not documented previously what happens when an `exec` command in an interactive rebase fails. Now we do. Signed-off-by: Johannes Schindelin --- Documentation/git-rebase.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) 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: -- gitgitgadget