From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: js/ci-coverity, was Re: What's cooking in git.git (Oct 2023, #02; Wed, 4)
Date: Thu, 05 Oct 2023 11:44:05 -0700 [thread overview]
Message-ID: <xmqqh6n4j4ei.fsf@gitster.g> (raw)
In-Reply-To: <20231005170859.GB975921@coredump.intra.peff.net> (Jeff King's message of "Thu, 5 Oct 2023 13:08:59 -0400")
Jeff King <peff@peff.net> writes:
> On Wed, Oct 04, 2023 at 04:45:34PM -0700, Junio C Hamano wrote:
>
>> * js/ci-coverity (2023-09-25) 7 commits
>> - SQUASH???
>> - coverity: detect and report when the token or project is incorrect
>> - coverity: allow running on macOS
>> - coverity: support building on Windows
>> - coverity: allow overriding the Coverity project
>> - coverity: cache the Coverity Build Tool
>> - ci: add a GitHub workflow to submit Coverity scans
>>
>> GitHub CI workflow has learned to trigger Coverity check.
>>
>> Looking good.
>> source: <pull.1588.v2.git.1695642662.gitgitgadget@gmail.com>
>
> I think that has been sitting at "Looking good" for a few iterations.
> IMHO it is ready to progress, with the SQUASH applied on the final
> patch.
Ah, yes, unless I use some magic phrase (like "Will merge to" or
"Expecting") there in the report, entries tend to be left in the
noise. Thanks for noticing and pinging. Very much appreciated.
prev parent reply other threads:[~2023-10-05 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 23:45 What's cooking in git.git (Oct 2023, #02; Wed, 4) Junio C Hamano
2023-10-05 17:08 ` js/ci-coverity, was " Jeff King
2023-10-05 18:44 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqh6n4j4ei.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).