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

From: phillip.wood@talktalk.net <phillip.wood@talktalk.net>
Date: Dec 21, 2017, 16:58 UTC
Message-ID: <27972213.1048151513875511767.JavaMail.defaultUser@defaultHost>
In-Reply-To: <xmqqshc6tm26.fsf@gitster.mtv.corp.google.com>

Show 5 quoted lines

>----Original Message----
>From: junio@pobox.com
>Date: 19/12/2017 22:00 
>To: <git@vger.kernel.org>
>Subj: What&#39;s cooking in git.git (Dec 2017, #04; Tue, 19)

Show 22 quoted lines

>* pw/sequencer-in-process-commit (2017-12-13) 10 commits
>  (merged to 'next' on 2017-12-13 at ec4d2b9c84)
> + sequencer: improve config handling
>  (merged to 'next' on 2017-12-06 at a4212f7ebd)
> + t3512/t3513: remove KNOWN_FAILURE_CHERRY_PICK_SEES_EMPTY_COMMIT=1
> + sequencer: try to commit without forking 'git commit'
> + sequencer: load commit related config
> + sequencer: simplify adding Signed-off-by: trailer
> + commit: move print_commit_summary() to libgit
> + commit: move post-rewrite code to libgit
> + Add a function to update HEAD after creating a commit
> + commit: move empty message checks to libgit
> + t3404: check intermediate squash messages
>
> 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'.

Can you hold this one in next for now please, I think there is a problem with freeing a statically allocated variable. I'll sort it out after Christmas

Thanks

Phillip