git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2020, #01; Tue, 3)
Date: Tue, 3 Mar 2020 15:05:54 -0800	[thread overview]
Message-ID: <20200303230554.GA11837@syl.local> (raw)
In-Reply-To: <xmqqimjl6pvn.fsf@gitster-ct.c.googlers.com>

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@ttaylorr.com/#t

  reply	other threads:[~2020-03-03 23:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 22:21 What's cooking in git.git (Mar 2020, #01; Tue, 3) Junio C Hamano
2020-03-03 23:05 ` Taylor Blau [this message]
2020-03-03 23:12   ` Junio C Hamano
2020-03-03 23:19     ` Junio C Hamano
2020-03-03 23:28       ` Taylor Blau
2020-03-04  3:31 ` Heba Waly
2020-03-04 15:30   ` Jonathan Tan
2020-03-04 16:18   ` Junio C Hamano
2020-03-05 15:17     ` Heba Waly
2020-03-06 17:23       ` [PATCH] update how-to-maintain-git Junio C Hamano
2020-03-06 19:06         ` Eric Sunshine
2020-03-06 21:28           ` Junio C Hamano
2020-03-07 12:16         ` Martin Ågren
2020-03-04 20:40 ` hv/receive-denycurrent-everywhere, was Re: What's cooking in git.git (Mar 2020, #01; Tue, 3) Johannes Schindelin
2020-03-04 21:27   ` Junio C Hamano

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=20200303230554.GA11837@syl.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@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).