Re: What's cooking in git.git (Dec 2017, #04; Tue, 19)

From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Date: Dec 20, 2017, 18:19 UTC
Message-ID: <9f58362a-c06c-5842-d22e-cc1ca165f0cf@gmail.com>
In-Reply-To: <xmqqshc6tm26.fsf@gitster.mtv.corp.google.com>

On Wednesday 20 December 2017 03:30 AM, Junio C Hamano wrote:

Show 11 quoted lines

> * pw/sequencer-in-process-commit (2017-12-13) 10 commits
>    (merged to 'next' on 2017-12-13 at ec4d2b9c84)
>    ...
>   The sequencer infrastructure is shared across "git cherry-pick",
>   "git rebase -i", etc., and has always spawned "git commit" when it
>   needs to create a commit.  It has been taught to do so internally,
>   when able, by reusing the codepath "git commit" itself uses, which
>   gives performance boost for a few tens of percents in some sample
>   scenarios.
> 
>   Will merge to 'master'.

I just encountered a small issue with 'rebase -i'. My bisection pointed at,

     28d6daed4 (sequencer: improve config handling, 2017-12-13)

So, I guess it would be better if you could delay merging it to 'master'. I'm not sure what how the commit and the patch are related but lets discuss that in the patch thread.

-- 
Kaartic