From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: "Phillip Wood" <phillip.wood123@gmail.com>,
"Josh Soref" <gitgitgadget@gmail.com>,
git@vger.kernel.org,
"Johannes Schindelin" <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] ci(*-leaks): skip the git-svn tests to save time
Date: Sat, 17 Jan 2026 16:35:09 -0800 [thread overview]
Message-ID: <xmqq5x8z69mq.fsf@gitster.g> (raw)
In-Reply-To: <de592bff-d7ac-41b5-bb24-4ced285a52e0@app.fastmail.com> (Kristoffer Haugsbakk's message of "Sat, 17 Jan 2026 20:02:16 +0100")
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
> On Sat, Jan 17, 2026, at 19:34, Junio C Hamano wrote:
>>>[snip]
>> Yup, I generally like this direction, and introducing NO_P4_TESTS
>> and NO_CVS_TESTS would not be so bad. Here is how it looks on top
>> of Dscho's patch.
>>
>> --- >8 ---
>> Subject: [PATCH] ci: skip CVS and P4 tests in leaks job, too
>>
>> Looking at the CI logs, the p4 and cvs tests account for another 24
>> minutes of test time and they offer minimal value for quite a
>> similar reason as the previous step.
>>
>> Let's introduce and use a mechanism to skip these tests to save
>> some resources.
>>
>> Suggested-by: Phillip Wood <phillip.wood123@gmail.com>
>
> Nitpick: Using the commit ident
>
> Phillip Wood <phillip.wood@dunelm.org.uk>
>
> might be slightly better?
I didn't even realize there are multiple addresses in play,
actually. I just took it from the e-mail header's Cc: field,
which my MUA copied from From: field of the message I was responding
to, which was the identity of the person who suggested the change
after all ;-).
So, I dunno.
next prev parent reply other threads:[~2026-01-18 0:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 17:31 [PATCH] ci(*-leaks): skip the git-svn tests to save time Johannes Schindelin via GitGitGadget
2026-01-16 19:20 ` Junio C Hamano
2026-01-17 15:04 ` Phillip Wood
2026-01-17 18:34 ` Junio C Hamano
2026-01-17 19:02 ` Kristoffer Haugsbakk
2026-01-18 0:35 ` Junio C Hamano [this message]
2026-01-20 10:31 ` Phillip Wood
2026-01-20 10:34 ` Phillip Wood
2026-01-20 15:42 ` Junio C Hamano
2026-01-23 14:47 ` Phillip Wood
2026-01-23 17:46 ` Junio C Hamano
2026-01-26 9:47 ` Phillip Wood
2026-01-26 16:06 ` 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=xmqq5x8z69mq.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=johannes.schindelin@gmx.de \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=phillip.wood123@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.