From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Mon, 01 Jul 2019 11:48:12 GMT
Subject: Re: [PATCH 1/1] Let rebase.reschedulefailedexec only affect interactive rebases
Message-ID: <nycvar.QRO.7.76.6.1907011346411.44@tvgsbejvaqbjf.bet>
In-Reply-To: <0F745CE4-3203-4447-B1D5-937CCDCC64C7@commonkarma.org>

Hi,

On Fri, 28 Jun 2019, Vas Sudanagunta wrote:

> It seems unintuitive that including a command to execute between each
> rebase merge implies an interactive rebase. It’s no more interactive
> than a sequence of rebase merges without intervening commands. A command
> failure interrupts a rebase just as a merge conflict does. If the fact
> that a rebase can be interrupts mid-sequence, then all rebases are
> interactive.

Indeed. I would consider it an implementation detail that the `--exec`
option uses the interactive rebase backend, and I would hate to force
users to know about this.

Ciao,
Johannes