From: Taylor Blau <me@ttaylorr.com>
To: Jeff King <peff@peff.net>
Cc: Philippe Blain <levraiphilippeblain@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Git mailing list <git@vger.kernel.org>
Subject: Re: [PATCH] p5332: drop "+" from --stdin-packs input
Date: Tue, 22 Apr 2025 13:24:18 -0400 [thread overview]
Message-ID: <aAfQwrhuLF7BysyE@nand.local> (raw)
In-Reply-To: <20250422111632.GA1855088@coredump.intra.peff.net>
On Tue, Apr 22, 2025 at 07:16:32AM -0400, Jeff King wrote:
> ---
> t/perf/p5332-multi-pack-reuse.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
My apologies for the mistake in the first place, but thank you for
digging and providing the fix.
Acked-by: Taylor Blau <me@ttaylorr.com>
Thanks,
Taylor
prev parent reply other threads:[~2025-04-22 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 2:01 Test failure in p5332-multi-pack-reuse.sh Philippe Blain
2025-04-22 4:06 ` Junio C Hamano
2025-04-22 11:16 ` [PATCH] p5332: drop "+" from --stdin-packs input Jeff King
2025-04-22 15:49 ` Junio C Hamano
2025-05-01 16:03 ` Jeff King
2025-04-22 17:24 ` 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=aAfQwrhuLF7BysyE@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=levraiphilippeblain@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).