Subject: Re: What's cooking in git.git (Mar 2020, #07; Sun, 22)

From: Taylor Blau <[email-masked]>
Date: Mon, 23 Mar 2020 13:16:02 -0600

Hi Junio,

On Sun, Mar 22, 2020 at 06:10:05PM -0700, Junio C Hamano wrote:
> Git 2.26 (final) has been tagged.

Thanks; your work to ensure that 2.26 was a success is much appreciated.
I wrote an accompanying blog post summarizing your release notes here:

  https://github.blog/2020-03-22-highlights-from-git-2-26/.

> * tb/commit-graph-split-merge (2020-03-05) 3 commits
>   (merged to 'next' on 2020-03-09 at f3aa7bb305)
>  + builtin/commit-graph.c: support '--input=none'
>  + builtin/commit-graph.c: introduce '--input=<source>'
>  + builtin/commit-graph.c: support '--split[=<strategy>]'
>
>  The code to write out the commit-graph has been taught a few
>  options to control if the resulting graph chains should be merged
>  or a single new incremental graph is created.
>
>  Will cook in 'next'.

I noticed that this has been cooking in 'next' for a few weeks now. Is
there anything you're looking for specifically before graduating this to
master?

For what it's worth, we've been running this patch at GitHub for a
little over a ~month and using these options in our repository
maintenance jobs.

Thanks,
Taylor