git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Junio C Hamano <junio@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2017, #04; Tue, 19)
Date: Wed, 20 Dec 2017 23:49:01 +0530	[thread overview]
Message-ID: <9f58362a-c06c-5842-d22e-cc1ca165f0cf@gmail.com> (raw)
In-Reply-To: <xmqqshc6tm26.fsf@gitster.mtv.corp.google.com>

On Wednesday 20 December 2017 03:30 AM, Junio C Hamano wrote:
> * 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

  reply	other threads:[~2017-12-20 18:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 22:00 What's cooking in git.git (Dec 2017, #04; Tue, 19) Junio C Hamano
2017-12-20 18:19 ` Kaartic Sivaraam [this message]
2017-12-21 16:58 ` phillip.wood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9f58362a-c06c-5842-d22e-cc1ca165f0cf@gmail.com \
    --to=kaartic.sivaraam@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junio@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).