From: Junio C Hamano <gitster@pobox.com>
To: "Philip Peterson via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Kristoffer Haugsbakk <code@khaugsbakk.name>,
Philip <philip.c.peterson@gmail.com>
Subject: Re: [PATCH v2] apply: add unit tests for parse_range
Date: Thu, 06 Jun 2024 10:24:18 -0700 [thread overview]
Message-ID: <xmqqle3im1bx.fsf@gitster.g> (raw)
In-Reply-To: <pull.1677.v2.git.git.1716710073910.gitgitgadget@gmail.com> (Philip Peterson via GitGitGadget's message of "Sun, 26 May 2024 07:54:33 +0000")
"Philip Peterson via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: Philip Peterson <philip.c.peterson@gmail.com>
>
> Also rename parse_range to parse_fragment_range for external linkage.
>
> Signed-off-by: Philip Peterson <philip.c.peterson@gmail.com>
> ---
This version saw no reviews (unfortunately).
I just gave another quick glance, did not spot anything glaringly
wrong, and the way the tests are organized as a series of ...
> + TEST(setup_static((struct test_case) {
> + .line = "@@ -4,4",
> + .offset = -1,
> + .expect_suffix = " +",
> + .expect_result = FAILURE,
> + .expect_p1 = 9999,
> + .expect_p2 = 9999
> + }), "negative offset");
... rather pleasant to read. I'd admit that it does not count as a
proper review, though.
Thanks.
next prev parent reply other threads:[~2024-06-06 17:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 4:45 [PATCH 0/2] apply: add unit tests for parse_range Philip Peterson via GitGitGadget
2024-02-19 4:45 ` [PATCH 1/2] apply: add unit tests for parse_range and rename to parse_fragment_range Philip Peterson via GitGitGadget
2024-02-19 21:35 ` Junio C Hamano
2024-04-04 3:53 ` Philip
2024-04-04 19:27 ` Junio C Hamano
2024-02-19 4:45 ` [PATCH 2/2] apply: rewrite unit tests with structured cases Philip Peterson via GitGitGadget
2024-02-19 21:49 ` Junio C Hamano
2024-02-19 22:04 ` Kristoffer Haugsbakk
2024-05-26 7:54 ` [PATCH v2] apply: add unit tests for parse_range Philip Peterson via GitGitGadget
2024-06-06 17:24 ` Junio C Hamano [this message]
2024-06-07 15:00 ` Phillip Wood
2024-06-07 16:59 ` 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=xmqqle3im1bx.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=philip.c.peterson@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.