All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: michael.opdenacker@bootlin.com, docs@lists.yoctoproject.org
Cc: rybczynska@gmail.com, mikko.rapeli@linaro.org
Subject: Re: [docs] [PATCH v2 1/4] ref-manual: variables.rst: add documentation for CVE_VERSION
Date: Wed, 26 Oct 2022 17:32:29 +0100	[thread overview]
Message-ID: <8cacc3686a7c813bffa48e17c0bc5d98976ab41e.camel@linuxfoundation.org> (raw)
In-Reply-To: <20221026160713.2068570-2-michael.opdenacker@bootlin.com>

On Wed, 2022-10-26 at 18:07 +0200, Michael Opdenacker via
lists.yoctoproject.org wrote:
> From: Michael Opdenacker <michael.opdenacker@bootlin.com>
> 
> From: Mikko Rapeli <mikko.rapeli@linaro.org>

I think your "From:" injection script may need a tweak to avoid two
entries!

Cheers,

Richard


  reply	other threads:[~2022-10-26 16:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1721A288D2BAB036.492@lists.yoctoproject.org>
2022-10-26 16:07 ` [PATCH v2 0/4] Improve CVE check and patching documentation michael.opdenacker
2022-10-26 16:07   ` [PATCH v2 1/4] ref-manual: variables.rst: add documentation for CVE_VERSION michael.opdenacker
2022-10-26 16:32     ` Richard Purdie [this message]
2022-10-26 17:51       ` [docs] " Michael Opdenacker
2022-10-26 16:07   ` [PATCH v2 2/4] ref-manual: classes.rst: improve documentation for cve-check.bbclass michael.opdenacker
2022-10-26 16:07   ` [PATCH v2 3/4] dev-manual: common-tasks.rst: add regular updates and CVE scans to security best practices michael.opdenacker
2022-10-26 16:07   ` [PATCH v2 4/4] dev-manual: common-tasks.rst: refactor and improve "Checking for Vulnerabilities" section michael.opdenacker
2022-10-27  6:54     ` Mikko Rapeli
2022-10-27  8:16       ` [docs] " 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=8cacc3686a7c813bffa48e17c0bc5d98976ab41e.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=michael.opdenacker@bootlin.com \
    --cc=mikko.rapeli@linaro.org \
    --cc=rybczynska@gmail.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 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.