Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2, 2/2] Replace LIBFOO_CPE_ID_NAME by LIBFOO_CPE_ID_PRODUCT
Date: Thu, 21 Jan 2021 22:44:36 +0100	[thread overview]
Message-ID: <20210121224436.1df7f6aa@windsurf.home> (raw)
In-Reply-To: <20210118174151.420304-2-fontaine.fabrice@gmail.com>

On Mon, 18 Jan 2021 18:41:51 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Replace LIBFOO_CPE_ID_NAME by LIBFOO_CPE_ID_PRODUCT to better "comply"
> with the official "Well-Formed CPE Name Data Model" parameters:
>  - https://csrc.nist.gov/publications/detail/nistir/7695/final
>  - https://nvlpubs.nist.gov/nistpubs/Legacy/IR/nistir7695.pdf
> 
> It should be noted that the following parameters could also be replaced
> in following commits to increase compliance with above specification:
>  - LIBFOO_CPE_ID_VERSION_MINOR -> LIBFOO_CPE_ID_UPDATE
>  - LIBFOO_CPE_ID_PREFIX -> LIBFOO_CPE_VERSION (i.e. 2.3) and
>    LIBFOO_CPE_ID_PART (a for applications, o for operating systems or h
>    for hardware)

This second paragraph doesn't really belong to a commit log, as it
talks about "other things that could be done".

So, I dropped this part of the commit, refreshed the patch to take into
account other CPE_ID_NAME variables that were introduced since then,
and applied.

Thanks!

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

  reply	other threads:[~2021-01-21 21:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 17:41 [Buildroot] [PATCH v2, 1/2] Revert "docs/manual: replace LIBFOO_CPE_ID_PRODUCT" Fabrice Fontaine
2021-01-18 17:41 ` [Buildroot] [PATCH v2, 2/2] Replace LIBFOO_CPE_ID_NAME by LIBFOO_CPE_ID_PRODUCT Fabrice Fontaine
2021-01-21 21:44   ` Thomas Petazzoni [this message]
2021-01-21 21:43 ` [Buildroot] [PATCH v2, 1/2] Revert "docs/manual: replace LIBFOO_CPE_ID_PRODUCT" 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=20210121224436.1df7f6aa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox