all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Léo Le Bouter" <lle-bout@zaclys.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Leo Famulari <leo@famulari.name>, Guix Devel <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 19:50:53 +0100	[thread overview]
Message-ID: <e1aa89721e6dc07459864bdb117b4663f9444d89.camel@zaclys.net> (raw)
In-Reply-To: <CAJ3okZ0nWAUz-=C5O9pZ2ZA4otdNrXfAwthXcimKoGPuKDcuSg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]

On Tue, 2021-03-16 at 19:46 +0100, zimoun wrote:
> Well, it seems better to send such changes to guix-patches, waiting
> 15
> days, and then if no comment, push.  It is what the manual describes:
> 
>         Non-trivial patches should always be posted to
>         guix-patches@gnu.org (trivial patches include fixing typos,
>         etc.). […]
> 
>         For patches that just add a new package, and a simple one,
> it’s OK to
>         commit, if you’re confident […].  Likewise for package
> upgrades, except
>         upgrades that trigger a lot of rebuilds […].
> 
>         […]
> 
>         […] If you didn’t receive any reply after two weeks, and if
>         you’re confident, it’s OK to commit.
> 
> <http://guix.gnu.org/manual/devel/en/guix.html#Commit-Access>
> 
> And from my understanding, it is a non-trivial patch which triggers a
> lot of rebuilds.  Double reasons. ;-)

It's not just like any other patch, it's a security patch, so **15**
days..

> 
> Cheers,
> simon

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-03-16 19:37 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 [this message]
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
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=e1aa89721e6dc07459864bdb117b4663f9444d89.camel@zaclys.net \
    --to=lle-bout@zaclys.net \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=zimon.toutoune@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.
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.