Re: [PATCH v2 1/2] rebase -i: clarify what happens on a failed `exec`
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Oct 12, 2018, 08:36 UTC
- Message-ID
- <nycvar.QRO.7.76.6.1810121036090.45@tvgsbejvaqbjf.bet>
- In-Reply-To
- <xmqqva68gaqz.fsf@gitster-ct.c.googlers.com>
Hi Junio & Eric,
On Thu, 11 Oct 2018, Junio C Hamano wrote:
Show 20 quoted lines
> Eric Sunshine <sunshine@sunshineco.com> writes: > > > On Wed, Oct 10, 2018 at 4:54 AM Johannes Schindelin via GitGitGadget > > <gitgitgadget@gmail.com> wrote: > >> 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> > >> --- > >> diff --git 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. Anz command that fails will interrupt the rebase, > >> + withe exit code 1. > > > > s/Anz/Any/ > > s/withe/with/
These tyopes will be fxied in the nxet itaretion.
Ciao, Dhsco
Show 8 quoted lines
> > Heh, I know I am not good at spelling, either, but hopefully I am a > bit more careful than leaving as many typoes as I have added lines > in my patch X-<. After all, it's not a race to send in patches as > quickly as possible. > > Queued. Thanks, both. >