From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Leo Famulari <leo@famulari.name>
Cc: "Léo Le Bouter" <lle-bout@zaclys.net>, guix-devel@gnu.org
Subject: Re: Release 1.2.1: zstd 1.4.4 -> 1.4.9: grafting or core-updates?
Date: Tue, 16 Mar 2021 21:53:01 +0100 [thread overview]
Message-ID: <87ft0un7ma.fsf@nckx> (raw)
In-Reply-To: <YFDxLvQcaiJadhJJ@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
Hi L[ée]o,
Wow, Léo. You've done some seriously impressive CVE squashing in
such a short timespan, and I'm very grateful to have you on board.
Leo Famulari 写道:
> I do agree that updating this program 5 versions in a graft was
> perhaps
> too much.
>
> We should always try to cherry-pick bug-fix patches when
> grafting.
> Otherwise the risk of breakage is too high.
I agree. Whilst grafts are indispensible for timely deployment of
security patches, they're also a dirty hack composed entirely of
rough edges.
They exist for one purpose: patch out known vulnerabilities.
Every extra change not strictly required for security is a
liability.
We sometimes get away with grafting entire releases (OpenSSL comes
to mind), but this is not an ideal to emulate.
> At least, these types of patches should be reviewed on
> guix-patches.
> Léo, can you send them to guix-patches in the future?
I have the same request :-) Please submit non-trivial patches for
review (and, unfortunately, grafts are hardly ever trivial). This
isn't a comment on your work; it's our standard way of doing
things.
I know we're not the #1 bestest project when it comes to the swift
review of patches. I understand the sense of urgency in fixing
things that one feels should have been fixed long ago. Thank you
for helping us to improve on both points.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-03-16 20:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 5:09 GNU Guix (pull?) on i686 broke after zstd grafting Léo Le Bouter
2021-03-06 5:30 ` Léo Le Bouter
2021-03-10 10:37 ` Ludovic Courtès
2021-03-10 10:43 ` Léo Le Bouter
2021-03-11 2:11 ` Léo Le Bouter
2021-03-11 9:37 ` zimoun
2021-03-11 9:40 ` Léo Le Bouter
2021-03-11 9:58 ` zimoun
2021-03-11 10:05 ` Léo Le Bouter
2021-03-16 16:34 ` Release 1.2.1: zstd 1.4.4 -> 1.4.9: grafting or core-updates? zimoun
2021-03-16 17:06 ` Léo Le Bouter
2021-03-16 17:48 ` Leo Famulari
2021-03-16 18:03 ` Léo Le Bouter
2021-03-16 17:59 ` zimoun
2021-03-16 17:55 ` Leo Famulari
2021-03-16 18:08 ` Léo Le Bouter
2021-03-16 18:46 ` zimoun
2021-03-16 18:50 ` Léo Le Bouter
2021-03-16 19:04 ` zimoun
2021-03-16 18:19 ` zimoun
2021-03-16 18:26 ` Léo Le Bouter
2021-03-16 19:18 ` Leo Famulari
2021-03-16 19:25 ` zimoun
2021-03-16 19:29 ` Leo Famulari
2021-03-16 21:46 ` Security-czar needed? WAS: " Bengt Richter
2021-03-16 22:03 ` Leo Famulari
2021-03-17 6:24 ` Léo Le Bouter
2021-03-17 14:00 ` zimoun
2021-03-16 21:47 ` Maxime Devos
2021-03-16 20:53 ` Tobias Geerinckx-Rice [this message]
2021-03-16 21:18 ` Vincent Legoll
2021-03-16 21:56 ` Leo Famulari
2021-03-17 6:40 ` Léo Le Bouter
2021-03-30 0:35 ` Léo Le Bouter
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=87ft0un7ma.fsf@nckx \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=lle-bout@zaclys.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.