All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/netcat: set NETCAT_CPE_ID_VALID
Date: Mon, 11 Jan 2021 21:32:08 +0100	[thread overview]
Message-ID: <20210111213208.05cb371a@windsurf.home> (raw)
In-Reply-To: <20210111201544.1414785-1-fontaine.fabrice@gmail.com>

Hello Fabrice,

On Mon, 11 Jan 2021 21:15:44 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

Thanks for all those CPE related patches, very useful. Since you're
doing all those checks, perhaps it would be useful to have a pointer to
something that confirms how you have validated a given CPE. Either in
the commit log, or as a comment in the .mk file? Perhaps a comment in
the commit log is sufficient?

Since you're doing the research, I guess it should be quite easy to add
such a reference in the commit log. Maybe something such as:

https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.3&keyword=cpe%3A2.3%3Aa%3Anetcat_project%3Anetcat

Note: no need to resend existing patches for this. This is just a
suggestion for future patches.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2021-01-11 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 20:15 [Buildroot] [PATCH 1/1] package/netcat: set NETCAT_CPE_ID_VALID Fabrice Fontaine
2021-01-11 20:32 ` Thomas Petazzoni [this message]
2021-01-11 20:33 ` Thomas Petazzoni

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=20210111213208.05cb371a@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.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 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.