public inbox for git@vger.kernel.org 
 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, #02; Thu, 5)
Date: Thu, 5 Mar 2020 14:08:58 -0800	[thread overview]
Message-ID: <20200305220858.GA61427@syl.local> (raw)
In-Reply-To: <xmqq4kv24fzo.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Thu, Mar 05, 2020 at 02:02:51PM -0800, Junio C Hamano wrote:
> [Cooking]
>
> * tb/commit-graph-split-merge (2020-03-05) 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.
>
>  .

I noticed that this didn't quite make the cut for -rc0, but I'm
wondering what the status of it is, since I haven't seen '.' alone like
this in your mail before.

(It may be that you forgot to write the thing that was to come before
the '.', but I would like to know what its status is either way). In the
last What's Cooking, we discussed [2] going forward with it, but I'm
happy to wait until a later -rc or release if things have changed.

Thanks,
Taylor

[2]: https://lore.kernel.org/git/20200303230554.GA11837@syl.local/

  reply	other threads:[~2020-03-05 22:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05 22:02 What's cooking in git.git (Mar 2020, #02; Thu, 5) Junio C Hamano
2020-03-05 22:08 ` Taylor Blau [this message]
2020-03-06 17:29 ` Thomas Gummerer
2020-03-06 17:54   ` Junio C Hamano
2020-03-10 16:13     ` Thomas Gummerer

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=20200305220858.GA61427@syl.local \
    --to=me@ttaylorr$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitster@pobox$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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