Re: [PATCH v2 00/18] builtin rebase options

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 6, 2018, 20:38 UTC
Message-ID: <xmqqin3iz7ik.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <xmqqmusuz9ql.fsf@gitster-ct.c.googlers.com>

Junio C Hamano <gitster@pobox.com> writes:

Show 5 quoted lines

> I've rebuilt the collection of topics up to pk/rebase-in-c-6-final
> with these two updated series twice, once doing it manually, like I
> did the last time, and another using "rebase -i -r" on top of the
> updated pk/rebase-in-c-4-opts.  The resulting trees match, of
> course.

Just to clarify, "trees match" means "'rebase -i -r' gave us the correct result" ;-).

> I guess that is the answer to a question you asked earlier, which I
> haven't answered so far because I didn't have a good grasp of where
> my preference was coming from when it was asked.  Now I know, so...

In case the question was unclear it was "is there a reason why you do not want to use rebase -ir?"

If "cherry-pick" did not lose notes, I would have preferred to do this kind of rebuilding dependent chains of topics without using rebase at all, but that is a different story.