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 (Mar 2020, #10; Tue, 31)
Date: Fri, 03 Apr 2020 15:13:48 -0700	[thread overview]
Message-ID: <xmqqmu7sxlnn.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200403200418.GA58491@syl.local> (Taylor Blau's message of "Fri, 3 Apr 2020 14:04:18 -0600")

Taylor Blau <me@ttaylorr.com> writes:

> On Tue, Mar 31, 2020 at 04:04:28PM -0700, Junio C Hamano wrote:
>> * tb/commit-graph-split-merge (2020-03-24) 3 commits
>>   (merged to 'next' on 2020-03-31 at 2183baf09c)
>>  + builtin/commit-graph.c: support '--input=graphed'
>>  + 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 merge to 'master'.
>
> I know that this series has been cooking for a while (and that I've
> nagged you about merging it down to master), but I think I may ask you
> to temporarily eject it until I can send some more patches on top.

I'll mark in as "On hold" and throw it in the stalled bin ;-)

  reply	other threads:[~2020-04-03 22:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31 23:04 What's cooking in git.git (Mar 2020, #10; Tue, 31) Junio C Hamano
2020-04-02  6:56 ` Miriam R.
2020-04-02 17:42   ` Junio C Hamano
2020-04-02 12:42 ` Garima Singh
2020-04-02 17:40   ` Junio C Hamano
2020-04-02 16:10 ` Phillip Wood
2020-04-03 20:04 ` Taylor Blau
2020-04-03 22:13   ` Junio C Hamano [this message]
2020-04-03 22:56 ` Emily Shaffer

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=xmqqmu7sxlnn.fsf@gitster.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).