From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH v2] ci(linux-asan-ubsan): let's save some time
Date: Tue, 29 Aug 2023 23:19:57 -0700 [thread overview]
Message-ID: <xmqqsf819hma.fsf@gitster.g> (raw)
In-Reply-To: <20230830002801.GB227310@coredump.intra.peff.net> (Jeff King's message of "Tue, 29 Aug 2023 20:28:01 -0400")
Jeff King <peff@peff.net> writes:
> On Tue, Aug 29, 2023 at 08:47:28PM +0000, Johannes Schindelin via GitGitGadget wrote:
>
>> This commit is an attempt to reduce the pain and suffering stemming from
>> this particular job, simply by deciding that the benefit of running the
>> Python/Subversion-related tests in that job is far outweighed by its
>> cost.
>
> FWIW, I am in favor of this patch. I've had the same thought many times
> but was worried I was being too dismissive of p4/svn (which I personally
> do not care at all about). Omitting them from the sanitizer job (but
> still running the basic svn/p4 tests elsewhere) seems like a good
> compromise.
Exactly my feeling. Thanks, both.
prev parent reply other threads:[~2023-08-30 6:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 10:29 [PATCH] ci(linux-asan-ubsan): let's save some time Johannes Schindelin via GitGitGadget
2023-08-29 16:49 ` Junio C Hamano
2023-08-29 20:47 ` [PATCH v2] " Johannes Schindelin via GitGitGadget
2023-08-29 21:51 ` Junio C Hamano
2023-08-30 0:28 ` Jeff King
2023-08-30 6:19 ` Junio C Hamano [this message]
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=xmqqsf819hma.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=johannes.schindelin@gmx.de \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).