From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH buildroot-test] utils/daily-mail: implement CVE notification
Date: Fri, 10 Apr 2020 22:04:18 +0200 [thread overview]
Message-ID: <20200410220418.0ea274eb@windsurf.home> (raw)
In-Reply-To: <20200218025002.111059-1-thomas.petazzoni@bootlin.com>
On Tue, 18 Feb 2020 03:50:02 +0100
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> This commit improves the daily-mail script so that it uses the
> recently added CVE information in the JSON output of pkg-stats to send
> CVE-related notifications to the Buildroot mailing list and to
> individual maintainers of Buildroot packages.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
> utils/daily-mail | 65 +++++++++++++++++++++++++++++++++++++++++++-----
> 1 file changed, 59 insertions(+), 6 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-04-10 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 2:50 [Buildroot] [PATCH buildroot-test] utils/daily-mail: implement CVE notification Thomas Petazzoni
2020-04-10 20:04 ` Thomas Petazzoni [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=20200410220418.0ea274eb@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.