Re: [PATCH v4 0/8] Reimplement rebase --merge via interactive machinery
- From
Elijah Newren <newren@gmail.com>
- Date
- Jan 18, 2019, 18:07 UTC
- Message-ID
- <CABPp-BFRkg7HShJ-Noh=GKJUCh7TO7NpveX5Yy8Pv+1wZiH3qA@mail.gmail.com>
- In-Reply-To
- <xmqqmunxluj8.fsf@gitster-ct.c.googlers.com>
On Fri, Jan 18, 2019 at 9:55 AM Junio C Hamano <gitster@pobox.com> wrote:
Show 10 quoted lines
> > Johannes Schindelin <Johannes.Schindelin@gmx.de> writes: > > > I am about to submit a new iteration of my patch series, would it be too > > much trouble for you to rebase on top? If it would be, let me know, then I > > will rebase on top of yours. > > Or both of you keep the topics as-is and self-consistent, and let > the rerere machinery to squash it in when the two topics gets > merged.
Yeah, I see that commit 8d808e12a2cc ("Merge branch 'js/rebase-am' into jch", 2019-01-17) has my fix squashed in; thanks Junio.
I'm happy to do whatever is needed with en/rebase-merge-on-sequencer that makes it easiest for everyone else. I'm assuming right now that there's nothing I should do to improve it, but if anyone wants me to rebase it or fix something up, just let me know.