From: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>,
Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: "docs@lists.yoctoproject.org" <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] manuals: further documentation for cve-check
Date: Sat, 7 Aug 2021 03:33:24 +0000 [thread overview]
Message-ID: <d1d6b6d2e58b47b4a506f305403b5546@axis.com> (raw)
In-Reply-To: <a822bc10-12fa-8a68-3c22-d81c98b1672f@bootlin.com>
> -----Original Message-----
> From: docs@lists.yoctoproject.org <docs@lists.yoctoproject.org> On Behalf
> Of Michael Opdenacker
> Sent: den 6 augusti 2021 16:59
> To: Quentin Schulz <quentin.schulz@theobroma-systems.com>
> Cc: docs@lists.yoctoproject.org
> Subject: Re: [docs] [PATCH] manuals: further documentation for cve-check
>
> Hello Quentin,
>
> Preemptive nitpicking ;-)
>
> On 8/6/21 4:05 PM, Michael Opdenacker wrote:
> >
> >> Since CVE stands for "Common Vulnerabilities and Exposures", isn't
> >> adding vulnerabilities redundant?
Not much different from using, e.g., "a CD disc". ;)
> > Oh yes, agreed!
>
> Worse, CVE is already a plural acronym. So, we should use "CVE" instead
> of "CVEs", otherwise we're making a multi-plural! I'm sure you would
> have ended up noticing this.
That doesn't make sense. I would argue that "a CVE" is singular and refers
to one entry in the CVE database, regardless of what the acronym actually
stands for. Thus "bugs and CVEs" make sense, while "bugs and CVE" does not.
> Fortunately, not all readers are like you, but those are the best ones :-P
> Cheers,
> Michael.
//Peter
next prev parent reply other threads:[~2021-08-07 3:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 10:37 [PATCH] manuals: further documentation for cve-check Michael Opdenacker
2021-08-06 11:41 ` [docs] " Quentin Schulz
2021-08-06 14:05 ` Michael Opdenacker
[not found] ` <1698BCAA59B53D79.17952@lists.yoctoproject.org>
2021-08-06 14:58 ` Michael Opdenacker
2021-08-07 3:33 ` Peter Kjellerstedt [this message]
2021-08-09 8:21 ` Michael Opdenacker
[not found] <1698B15566F381B1.20643@lists.yoctoproject.org>
2021-08-06 10:43 ` Michael Opdenacker
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=d1d6b6d2e58b47b4a506f305403b5546@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=docs@lists.yoctoproject.org \
--cc=michael.opdenacker@bootlin.com \
--cc=quentin.schulz@theobroma-systems.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