Git development
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2026, #02)
Date: Mon, 11 May 2026 20:56:24 -0400	[thread overview]
Message-ID: <agJ6uADR6rVgddIW@nand.local> (raw)
In-Reply-To: <xmqq4iketzh0.fsf@gitster.g>

On Mon, May 11, 2026 at 12:08:27PM +0900, Junio C Hamano wrote:
> * tb/pseudo-merge-bugfixes (2026-04-21) 9 commits
>
> (snip)
>
>  Expecting (hopefully minor and final) reroll.
>  cf. <CABPp-BGkfavqezk2SV3+K6iF8MLm8j_=ijHiPDLmv_U_o_Ykgg@mail.gmail.com>
>  source: <cover.1776801694.git.me@ttaylorr.com>

I just sent[1] a reroll of this one, which should be ready to go.

> * tb/incremental-midx-part-3.3 (2026-04-29) 16 commits
>
> (snip)
>
>  Will merge to 'next'?
>  source: <cover.1777507303.git.me@ttaylorr.com>

I think that this one is as ready as it will be. Peff reviewed v2[2] and
noted a couple of minor things which I addressed in v3. Peff's review of
v3 didn't note any further issues, so I think this is ready to go.

(+CC Peff here in case I'm misrepresenting his review.)

Thanks,
Taylor

[1]: <cover.1778546804.git.me@ttaylorr.com>
[1]: <20260429081030.GA1268740@coredump.intra.peff.net>
[2]: <20260501064640.GB2038915@coredump.intra.peff.net>

      parent reply	other threads:[~2026-05-12  0:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11  3:08 What's cooking in git.git (May 2026, #02) Junio C Hamano
2026-05-11  5:51 ` Junio C Hamano
2026-05-11 13:22 ` kh/name-rev-custom-format Kristoffer Haugsbakk
2026-05-12  0:56 ` Taylor Blau [this message]

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=agJ6uADR6rVgddIW@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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