From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2026, #05)
Date: Thu, 12 Mar 2026 21:24:10 -0700 [thread overview]
Message-ID: <xmqq7brg9x1x.fsf@gitster.g> (raw)
In-Reply-To: <20260313002431.GA3200726@coredump.intra.peff.net> (Jeff King's message of "Thu, 12 Mar 2026 20:24:31 -0400")
Jeff King <peff@peff.net> writes:
> On Thu, Mar 12, 2026 at 05:10:31PM -0700, Junio C Hamano wrote:
>
>> * mf/apply-p-no-atoi (2026-03-09) 1 commit
>> - apply.c: fix -p argument parsing
>>
>> "git apply -p<n>" parses <n> more carefully now.
>>
>> Will merge to 'next'.
>> source: <20260310050621.3849719-1-mroik@delayed.space>
>
> I think this is responsible for test failures on Windows in jch/seen,
> but I'm stumped as to why. You might want to hold off until we figure
> it out.
>
> From the output I doubt the code change is responsible, but failing
> tests in 'next' is annoying.
Thanks.
next prev parent reply other threads:[~2026-03-13 4:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 0:10 What's cooking in git.git (Mar 2026, #05) Junio C Hamano
2026-03-13 0:24 ` Jeff King
2026-03-13 4:24 ` Junio C Hamano [this message]
2026-03-16 9:34 ` Patrick Steinhardt
2026-03-16 22:07 ` Taylor Blau
2026-03-18 3:03 ` Jeff King
2026-03-18 16:36 ` 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=xmqq7brg9x1x.fsf@gitster.g \
--to=gitster@pobox.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