On Fri, Nov 30, 2018 at 6:16 AM Junio C Hamano <[email protected]> wrote: > > Johannes Schindelin <[email protected]> writes: > > > Hi Junio, > > > > On Fri, 30 Nov 2018, Junio C Hamano wrote: > > > >> * en/rebase-merge-on-sequencer (2018-11-08) 2 commits > >> - rebase: implement --merge via git-rebase--interactive > >> - git-rebase, sequencer: extend --quiet option for the interactive > >> machinery > >> > >> "git rebase --merge" as been reimplemented by reusing the internal > >> machinery used for "git rebase -i". > > > > I *think* a new iteration has landed (which has 7 instead of 2 commits): > > https://public-inbox.org/git/[email protected]/ > > "Landed" as opposed to "be in-flight"? > > You got me worried by implying that I merged them to either 'master' > or 'next' where it is harder to back out ;-). > > During the freeze, especially after -rc1, I stop paying attention to > anything other than regression fixes and fixes to the addition since > the previous releases, unless I have too much time and get bored and > the new topic is trivial (which often means a single patch). > > I'll mark the topic with the following, and continue ignoring it (or > any other topics) for now. Thanks. > > * en/rebase-merge-on-sequencer (2018-11-08) 2 commits > - rebase: implement --merge via git-rebase--interactive > - git-rebase, sequencer: extend --quiet option for the interactive machinery > > "git rebase --merge" as been reimplemented by reusing the internal > machinery used for "git rebase -i". > > Reroll exists. > cf. <[email protected]>
I've also got a reroll with an extra patch to address Duy's feedback, an extra patch to make a small documentation clarification/correction, and a fix to a typo in a commit message from the last roll. But I'm waiting for 2.20.0 to be released before sending it.
