diff options
author | Johannes Schindelin <johannes.schindelin@gmx.de> | 2018-10-10 11:53:56 +0300 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2018-10-11 11:13:37 +0300 |
commit | b8c0b2100bbcbbfe324962b0f15c92207d945895 (patch) | |
tree | 8edaf07a8be7901eca2f731f20b1a2b245fbc2b7 /Documentation/git-rebase.txt | |
parent | 34b47315d9721a576b9536492cca0c11588113a2 (diff) |
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>
Diffstat (limited to 'Documentation/git-rebase.txt')
-rw-r--r-- | Documentation/git-rebase.txt | 3 |
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: |