From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: raid5atemyhomework <raid5atemyhomework@protonmail.com>
Cc: 46454@debbugs.gnu.org
Subject: [bug#46454] [PATCH] gnu: Update zfs.
Date: Sat, 13 Feb 2021 16:00:41 +0100 [thread overview]
Message-ID: <03733f98441a3ebe876a5dfd0c1d8494@tobias.gr> (raw)
In-Reply-To: <TjDF-9t9w3P5lOPGXn4yxmF2mAWG7JqPd_RMNtsMB4Ydy_x3fy6IvmEu8-OL74PNEifrvRuIAsnaWVbt6g_36Mt3r7myiuI2aauXEL6hIoM=@protonmail.com>
RAID,
On 2021-02-12 3:23, raid5atemyhomework via Guix-patches via wrote:
> Please prioritize, as this release fixes a (minor and low-probability)
> security issue:
Thank you very much for taking care of this!
To ensure that security updates stand out more, both on the list and in
the commit log, please use our (de facto?) standard commit message
format.
Instead of
gnu: Update zfs.
write
gnu: zfs: Update 2.0.3 [fixes CVE-0000-001].
or, if no CVE (or equivalent like TROVE) has yet been assigned:
gnu: zfs: Update 2.0.3 [security fixes].
Also note the changes to the rest of the subject.
Using this exact format makes it easi(er) to grep/automate the git log.
Everyone doing their own thing makes it hard.
Kind regards,
T G-R
Sent from a Web browser. Excuse or enjoy my brevity.
next prev parent reply other threads:[~2021-02-13 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 2:23 [bug#46454] [PATCH] gnu: Update zfs raid5atemyhomework via Guix-patches via
2021-02-12 5:57 ` bug#46454: " 宋文武
2021-02-13 15:00 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2021-02-13 16:18 ` [bug#46454] " Tobias Geerinckx-Rice via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=03733f98441a3ebe876a5dfd0c1d8494@tobias.gr \
--to=guix-patches@gnu.org \
--cc=46454@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=raid5atemyhomework@protonmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).