From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
Git mailing list <git@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] Make our clar tests ignore the long-tests argument
Date: Mon, 26 Oct 2026 09:10:38 -0700 [thread overview]
Message-ID: <xmqqzew0sarl.fsf@gitster.g> (raw)
In-Reply-To: <at8LHqyBm9Y0JE-1@pks.im> (Patrick Steinhardt's message of "Mon, 26 Oct 2026 09:11:10 +0100")
Patrick Steinhardt <ps@pks.im> writes:
> On Mon, Oct 26, 2026 at 01:01:03PM +0530, Kaartic Sivaraam wrote:
>> Changes in v2:
>> - Fixed the s/prerequiiste/prerequisite/ typo in the commit message
>>
>> - Link to v1: https://lore.kernel.org/r/20261022-ks-unit-tests-ignore-long-tests-v1-0-554a590d418b@gmail.com
>
> Thanks, this version looks good to me.
>
> Patrick
Thanks for writing and reviewing. Will queue.
next prev parent reply other threads:[~2026-10-26 16:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 11:01 [PATCH 0/2] Make our clar tests ignore the long-tests argument Kaartic Sivaraam
2026-10-22 11:01 ` [PATCH 1/2] unit-tests: reshuffle NOOP arguments to maintain order Kaartic Sivaraam
2026-10-23 6:50 ` Patrick Steinhardt
2026-10-22 11:01 ` [PATCH 2/2] unit-tests: ignore --long-tests Kaartic Sivaraam
2026-10-23 6:50 ` Patrick Steinhardt
2026-10-23 7:15 ` Kaartic Sivaraam
2026-10-26 7:31 ` [PATCH v2 0/2] Make our clar tests ignore the long-tests argument Kaartic Sivaraam
2026-10-26 7:31 ` [PATCH v2 1/2] unit-tests: reshuffle NOOP arguments to maintain order Kaartic Sivaraam
2026-10-26 7:31 ` [PATCH v2 2/2] unit-tests: ignore --long-tests Kaartic Sivaraam
2026-10-26 8:11 ` [PATCH v2 0/2] Make our clar tests ignore the long-tests argument Patrick Steinhardt
2026-10-26 16:10 ` Junio C Hamano [this message]
2026-10-27 17:44 ` Jeff King
-- strict thread matches above, loose matches on Subject: below --
2026-10-26 7:18 Kaartic Sivaraam
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=xmqqzew0sarl.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@gmail.com \
--cc=ps@pks.im \
/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.