Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: jaipaul.cheernam@est.tech,
	"patchtest@automation.yoctoproject.org"
	<patchtest@automation.yoctoproject.org>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Patchtest results for [PATCH] libseccomp: upgrade 2.6.0 -> 2.6.1
Date: Thu, 23 Jul 2026 17:02:34 +0200	[thread overview]
Message-ID: <2a1f01c9-e9ea-4233-9c0c-5f3d1d35dfc7@cherry.de> (raw)
In-Reply-To: <DU7PPF66507B2D750AF512C9E0859CF2513F3C02@DU7PPF66507B2D7.EURP189.PROD.OUTLOOK.COM>

Hi Jaipaul,

On 7/23/26 4:58 PM, Jaipaul Cheernam via lists.openembedded.org wrote:
>   Hi,
> 
> This is a false positive. The @v3 flagged by patchtest is from a verbatim upstream git log entry:
> 
>    8e31cd254be3 github: bump codeql version to @v3
> 
> It refers to a GitHub Actions version tag (actions/codeql-action@v3), not a GitHub username mention. I'd prefer to keep the upstream log intact rather than modify it.
> 

That's not the point. The point is that GitHub is stupid and will notify 
any GitHub user wherever and whenever their username appears in commit 
logs on GitHub. Considering we mirror our various git repos on GitHub, 
we have decided to stop having @xxx in commit logs due to many people 
complaining to us.

v3 is actually a valid GitHub username, see https://github.com/v3.

> Happy to resend with the @ stripped if maintainers prefer, but wanted to flag this as a patchtest false positive that might be worth addressing in the test itself.
> 

Please send a v2 with this fixed.

Thanks!
Quentin


  reply	other threads:[~2026-07-23 15:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 14:18 [PATCH] libseccomp: upgrade 2.6.0 -> 2.6.1 Jaipaul Cheernam
2026-07-23 14:31 ` Patchtest results for " patchtest
2026-07-23 14:58   ` Jaipaul Cheernam
2026-07-23 15:02     ` Quentin Schulz [this message]
2026-07-23 15:02 ` Jaipaul Cheernam
2026-07-23 15:31 ` [PATCH v2] " Jaipaul Cheernam

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=2a1f01c9-e9ea-4233-9c0c-5f3d1d35dfc7@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=jaipaul.cheernam@est.tech \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=patchtest@automation.yoctoproject.org \
    /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