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
