Hi Junio, On Tue, 29 Oct 2019, Junio C Hamano wrote: > Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > > > As the bug was introduced in this cycle, I would like to see the bug fix > > in v2.24.0, though;... > > Do you mean that before the change you blame for the "bug" things > worked better than what we have at the tip of 'master', or do you > mean that the change you blame for the "bug" changed the behaviour > relative to the previous released version but the updated behavior > is not what you consider correct? What I mean is this: previously, when an interactive rebase interrupted due to a now-empty patch, the advice given was correct, of clunky. Now it is incorrect. (Previously, the advice was to `git reset`, which was not completely helpful, but now it suggests to `git cherry-pick --continue`, which is incorrect.) Ciao, Dscho
