From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabien Lehoussel via buildroot <buildroot@buildroot.org>
Cc: Fabien Lehoussel <fabien.lehoussel@smile.fr>,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/gcc/gcc-final.mx: fix CPE identification
Date: Wed, 30 Jul 2025 22:49:40 +0200 [thread overview]
Message-ID: <20250730224940.516d9707@windsurf> (raw)
In-Reply-To: <20250716100712.1244865-1-fabien.lehoussel@smile.fr>
Hello Fabien,
Your commit title said "gcc-final.mx" which is not correct, it's
"gcc-final.mk", but anyway we generally just give the package name, so:
"package/gcc/gcc-final: ..." was enough.
On Wed, 16 Jul 2025 12:07:11 +0200
Fabien Lehoussel via buildroot <buildroot@buildroot.org> wrote:
> Fix the CPE (Common Platform Enumeration) identification in the gcc-final package to ensure proper vulnerability tracking.
Commit messages should be wrapped to ~72-80 columns. Also, we like to
give a link to the NVD database showing that the CPE identifier being
added is indeed correct. So I've added:
https://nvd.nist.gov/products/cpe/search/results?keyword=cpe:2.3:a:gnu:gcc
and applied to master. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-07-30 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 10:07 [Buildroot] [PATCH 1/1] package/gcc/gcc-final.mx: fix CPE identification Fabien Lehoussel via buildroot
2025-07-30 20:49 ` Thomas Petazzoni via buildroot [this message]
2025-08-07 18:24 ` Thomas Perale via buildroot
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=20250730224940.516d9707@windsurf \
--to=buildroot@buildroot.org \
--cc=fabien.lehoussel@smile.fr \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox