From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Anthony Wang <anthonywang513@gmail.com>, git@vger.kernel.org
Subject: Re: aw/t9811-modernize, was Re: What's cooking in git.git (Apr 2025, #04; Tue, 15)
Date: Fri, 18 Apr 2025 14:38:32 -0700 [thread overview]
Message-ID: <xmqqtt6l9mlj.fsf@gitster.g> (raw)
In-Reply-To: <20250418213531.GA89733@coredump.intra.peff.net> (Jeff King's message of "Fri, 18 Apr 2025 17:35:31 -0400")
Jeff King <peff@peff.net> writes:
> So I don't know if git-p4 got smarter, or what. But we should probably
> back out at least that part of the commit until we figure out what's
> going on (where "we" is somebody who cares a lot more about p4 than I
> do).
Yes, and there was another breakage in that 2-hunk patch in the
other hunk I sent out a fix for a few minutes ago.
Thanks.
next prev parent reply other threads:[~2025-04-18 21:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 23:41 What's cooking in git.git (Apr 2025, #04; Tue, 15) Junio C Hamano
2025-04-16 23:18 ` Ramsay Jones
2025-04-18 21:35 ` aw/t9811-modernize, was " Jeff King
2025-04-18 21:38 ` Junio C Hamano [this message]
2025-04-18 21:44 ` Junio C Hamano
2025-04-18 21:57 ` Jeff King
2025-04-22 5:47 ` Patrick Steinhardt
2025-04-22 14:50 ` Junio C Hamano
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=xmqqtt6l9mlj.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=anthonywang513@gmail.com \
--cc=git@vger.kernel.org \
--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).