From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Mikko Rapeli <mikko.rapeli@linaro.org>
Cc: docs@lists.yoctoproject.org, rybczynska@gmail.com
Subject: Re: [docs] [PATCH v2 4/4] dev-manual: common-tasks.rst: refactor and improve "Checking for Vulnerabilities" section
Date: Thu, 27 Oct 2022 10:16:54 +0200 [thread overview]
Message-ID: <c6b589e3-1c12-e1db-200c-d0c3ff1972b9@bootlin.com> (raw)
In-Reply-To: <Y1orJ5GKSJUCbf/z@nuoska>
Hi Mikko
On 10/27/22 08:54, Mikko Rapeli wrote:
> Now it looks good to me. Thanks for the review and new version!
Thanks for reviewing your text once again!
I fixed all the new issues you reported.
Cheers and thanks again for these very useful improvements to the
documentation.
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2022-10-27 8:16 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 ` [docs] " Richard Purdie
2022-10-26 17:51 ` 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 ` Michael Opdenacker [this message]
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=c6b589e3-1c12-e1db-200c-d0c3ff1972b9@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox