From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: bug in en/header-split-cache-h-part-3, was Re: What's cooking in git.git (Jun 2023, #05; Tue, 20)
Date: Fri, 23 Jun 2023 09:38:07 -0700 [thread overview]
Message-ID: <xmqqr0q2b0cw.fsf@gitster.g> (raw)
In-Reply-To: <CABPp-BEQ0_UfUbdeFetCsvAnpO_=mvmjQk8JS0trKJtCL=uh1A@mail.gmail.com> (Elijah Newren's message of "Thu, 22 Jun 2023 23:33:24 -0700")
Elijah Newren <newren@gmail.com> writes:
> Anyway, your rebase of en/header-split-cache-h-part-3, including
> Dscho's and Peff's changes, all look good to me.
>
> Thanks everyone!
Thanks for confirming. Let's merge it down to 'next' then.
next prev parent reply other threads:[~2023-06-23 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 0:04 What's cooking in git.git (Jun 2023, #05; Tue, 20) Junio C Hamano
2023-06-21 8:55 ` bug in en/header-split-cache-h-part-3, was " Jeff King
2023-06-21 17:05 ` Junio C Hamano
2023-06-21 20:26 ` Jeff King
2023-06-21 22:03 ` Junio C Hamano
2023-06-23 6:33 ` Elijah Newren
2023-06-23 16:38 ` Junio C Hamano [this message]
2023-06-24 1:25 ` Jeff King
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=xmqqr0q2b0cw.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.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;
as well as URLs for NNTP newsgroup(s).