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: Christian Couder <christian.couder@gmail.com>,
	Elijah Newren <newren@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	John Cai <johncai86@gmail.com>, git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Aug 2023, #01; Wed, 2)
Date: Mon, 7 Aug 2023 12:22:45 -0400	[thread overview]
Message-ID: <ZNEaVefeE86s2V6h@nand.local> (raw)
In-Reply-To: <xmqqv8dqhlkz.fsf@gitster.g>

On Mon, Aug 07, 2023 at 09:19:08AM -0700, Junio C Hamano wrote:
> >> However in a recent article
> >> (https://github.blog/2023-07-27-scaling-merge-ort-across-github/)
> >> GitHub says that they are already using git-replay (though not sure
> >> it's this exact version or another one), and GitLab plans to use it
> >> too.
>
> So there are plenty folks who are capable of reviewing but they are
> not interested in giving it to the general public by withholding
> their reviews ;-)?

I think the most capable reviewer would be Johannes, who was most
involved the Git-related parts of this work at GitHub.

I was party to most of the changes that went through in this area, but
didn't look closely.

Thanks,
Taylor

  reply	other threads:[~2023-08-07 16:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 18:10 What's cooking in git.git (Aug 2023, #01; Wed, 2) Junio C Hamano
2023-08-02 19:09 ` jt/path-filter-fix (was: Re: What's cooking in git.git (Aug 2023, #01; Wed, 2)) Taylor Blau
2023-08-02 19:20   ` jt/path-filter-fix Junio C Hamano
2023-08-02 19:28     ` jt/path-filter-fix Taylor Blau
     [not found] ` <CAP8UFD1vuB2kRr890B7GXum9HAMjRep86zy2tE4yE2C3W5QGHA@mail.gmail.com>
2023-08-07 12:41   ` What's cooking in git.git (Aug 2023, #01; Wed, 2) Christian Couder
2023-08-07 16:19     ` Junio C Hamano
2023-08-07 16:22       ` Taylor Blau [this message]
2023-08-07 16:56       ` Elijah Newren
2023-08-17 13:21         ` Johannes Schindelin
2023-08-07 20:59 ` Rubén Justo
2023-08-08 19:22 ` leak in jt/path-filter-fix, was " Jeff King
2023-08-08 19:25   ` Jeff King
2023-08-08 20:22   ` Taylor Blau
2023-08-08 21:19     ` Jeff King
2023-08-11 22:15     ` Jonathan Tan

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=ZNEaVefeE86s2V6h@nand.local \
    --to=me@ttaylorr.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johncai86@gmail.com \
    --cc=newren@gmail.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).