From: Junio C Hamano <gitster@pobox.com>
To: Mirko Faina <mroik@delayed.space>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: [PATCH v4] apply.c: fix -p argument parsing
Date: Thu, 12 Mar 2026 21:39:47 -0700 [thread overview]
Message-ID: <xmqqtsuk8hrg.fsf@gitster.g> (raw)
In-Reply-To: <20260313031950.1695103-1-mroik@delayed.space> (Mirko Faina's message of "Fri, 13 Mar 2026 04:19:47 +0100")
Mirko Faina <mroik@delayed.space> writes:
> As Jeff pointed out, the previous patch doesn't pass tests on windows...
> Inlined as a workaround and to avoid adding additional folders to the
> existing test directory.
Thanks for working very well together.
> +test_expect_success 'git apply -p 1 patch' '
> + cat >patch <<-\EOF &&
> + From 90ad11d5b2d437e82d4d992f72fb44c2227798b5 Mon Sep 17 00:00:00 2001
> + From: Mroik <mroik@delayed.space>
> + Date: Mon, 9 Mar 2026 23:25:00 +0100
> + Subject: [PATCH] Test
> +
> + ---
> + t/test/test | 0
> + 1 file changed, 0 insertions(+), 0 deletions(-)
> + create mode 100644 t/test/test
> +
> + diff --git a/t/test/test b/t/test/test
> + new file mode 100644
> + index 0000000000..e69de29bb2
> + --
> + 2.53.0.851.ga537e3e6e9
> +
> + EOF
It is more customary to indent the here-doc body to the same level
as surrounding <<EOF..EOF; no need to resend only to fix this, as I
can easily dedent it by one level.
> + test_when_finished "rm -rf t" &&
> + git apply -p 1 patch &&
> + test_path_is_dir t
> +'
> +
> +test_expect_success 'apply fails due to non-num -p' '
> + test_when_finished "rm -rf t test" &&
> + test_must_fail git apply -p malformed patch
> +'
> +
> +test_expect_success 'apply fails due to trailing non-digit in -p' '
> + test_when_finished "rm -rf t test" &&
> + test_must_fail git apply -p 2q patch
> +'
> +
> +test_expect_success 'apply fails due to negative number in -p' '
> + test_when_finished "rm -rf t test patch" &&
> + test_must_fail git apply -p -1 patch
> +'
The test all make sense, but if we know what error message we are
expecting, it may not be a bad idea to do something like
test_must_fail git apply -p -1 patch 2>err &&
test_grep "<num> has to be a non-negative" err
to ensure that the command did not fail for a wrong reason.
THanks.
next prev parent reply other threads:[~2026-03-13 4:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 23:26 [PATCH] apply.c: fix -p argument parsing Mirko Faina
2026-03-09 23:43 ` Junio C Hamano
2026-03-10 0:54 ` [PATCH v2] " Mirko Faina
2026-03-10 3:31 ` Junio C Hamano
2026-03-10 4:45 ` Mirko Faina
2026-03-10 5:06 ` [PATCH v3] " Mirko Faina
2026-03-10 13:13 ` Junio C Hamano
2026-03-13 0:16 ` Jeff King
2026-03-13 1:12 ` Jeff King
2026-03-13 1:29 ` Jeff King
2026-03-13 4:27 ` Junio C Hamano
2026-03-13 4:19 ` Junio C Hamano
2026-03-13 3:19 ` [PATCH v4] " Mirko Faina
2026-03-13 4:39 ` Junio C Hamano [this message]
2026-03-16 0:51 ` [PATCH] " Mirko Faina
2026-03-16 0:52 ` Mirko Faina
2026-03-16 19:56 ` Junio C Hamano
2026-03-15 17:22 ` Tian Yuchen
2026-03-15 17:56 ` Mirko Faina
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=xmqqtsuk8hrg.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mroik@delayed.space \
--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