git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2020, #04; Mon, 17)
Date: Wed, 19 Feb 2020 13:51:49 -0800	[thread overview]
Message-ID: <xmqqy2syckju.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20200219195822.GA5101@syl.local> (Taylor Blau's message of "Wed, 19 Feb 2020 11:58:22 -0800")

Taylor Blau <me@ttaylorr.com> writes:

> On Mon, Feb 17, 2020 at 02:08:38PM -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 discussion is still "settling", although the thread
> hasn't had any activity for a few days now.
>
> I wanted to get feedback from my response to Eric Sunshine before saying
> that we have consensus, but otherwise I think this is moving along.

Did you mean Szeder?

https://lore.kernel.org/git/cover.1581486293.git.me@ttaylorr.com/


  parent reply	other threads:[~2020-02-19 21:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 22:08 What's cooking in git.git (Feb 2020, #04; Mon, 17) Junio C Hamano
2020-02-18  3:30 ` Elijah Newren
2020-02-18 16:00   ` en/rebase-backend, was " Johannes Schindelin
2020-02-26 10:34     ` Alban Gruin
2020-02-22  3:11   ` Elijah Newren
2020-02-22 17:18     ` Junio C Hamano
2020-02-19 19:58 ` Taylor Blau
2020-02-19 20:50   ` Eric Sunshine
2020-02-19 21:51   ` Junio C Hamano [this message]
2020-02-19 22:07     ` Taylor Blau
2020-02-21 16:26 ` Phillip Wood
2020-02-22  3:03   ` Elijah Newren
2020-02-22 17:16     ` Junio C Hamano
2020-02-26 20:04     ` Elijah Newren

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=xmqqy2syckju.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).