Re: [PATCH v2 0/2] Work on t3404 in preparation for rebase--helper
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- May 16, 2016, 06:33 UTC
- Message-ID
- <alpine.DEB.2.20.1605160830340.3303@virtualbox>
- In-Reply-To
- <xmqqa8jtaliw.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Fri, 13 May 2016, Junio C Hamano wrote:
Show 23 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes: > > > On Thu, 12 May 2016, Junio C Hamano wrote: > > > >> I took these separately already, and plan to fast-track them as they > >> are both "trivially correct"; I double checked that what I have match > >> these two, too. > > > > Oh, okay. I just wanted to make things easier for you, and now that I > > have a script to prepare patch series, it's really almost as trivial > > for me to send out a new iteration as it would be to update a Pull > > Request on GitHub. > > > > Do you want me to hold off with new iterations in the future until you > > clarified your preferred course of action? > > No. You've been doing great. I just wanted to clarify what I did > to your patch before I merge them separately to 'next' ahead of the > remainder that you'd be sending out, expecting a possible course > correction, e.g. "that would make it harder to queue the other patches > yet to come, all of which would depend on both of them--it would be > better to queue them on a single topic to be extended with these > other patches, after all these two are not that urgent".
Thanks.
I planned to work on the remainder as a "topic thicket" using my Git garden shears [*1*] anyway, picking up the changes you picked up, replacing my original patches.
Ciao, Dscho
Footnote *1*: The garden shears are kind of a `git rebase -i -p` as I wish I had designed it originally. Thet live here: https://github.com/git-for-windows/build-extra/blob/master/shears.sh