Re: What's cooking in git.git (Mar 2020, #01; Tue, 3)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Junio,

On Tue, Mar 03, 2020 at 02:21:48PM -0800, Junio C Hamano wrote:
> * tb/commit-graph-split-merge (2020-02-12) 3 commits
>  - 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.
>
>  Waiting for the discussion to settle.
>  cf. <20200212205028.GE4364@syl.local>

I think that this may be as settled as this discussion is going to
reasonably get. I noticed that this has been on the "What's Cooking" as
waiting for the discussion to cool down, but there haven't been any new
messages.

I think that the options are probably unlikely to change in the future,
and unless there are some serious reservations that nobody has raised,
that we should go forward with the patches as they are.

What's in 'v3' of that series [1] is ready to merge, in my opinion.


Thanks,
Taylor

[1]: https://lore.kernel.org/git/cover.1581486293.git.me@xxxxxxxxxxxx/#t



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux