From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel@gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: Re: 03/03: doc: Update to cover for an additional OpenPGP signing key.
Date: Tue, 04 May 2021 11:08:24 +0200 [thread overview]
Message-ID: <874kfisw6v.fsf@gnu.org> (raw)
In-Reply-To: <20210504033513.A0CFA20D0E@vcs0.savannah.gnu.org> (guix-commits@gnu.org's message of "Mon, 3 May 2021 23:35:13 -0400 (EDT)")
Hi!
guix-commits@gnu.org skribis:
> commit 0f583f60f882d74f4cf2332c85343a2db67410c7
> Author: Maxim Cournoyer <maxim.cournoyer@gmail.com>
> AuthorDate: Sat May 1 22:35:09 2021 -0400
>
> doc: Update to cover for an additional OpenPGP signing key.
>
> The upcoming 1.3.0 release will be signed with my OpenPGP key; subsequent
> releases may also be.
>
> * doc/guix.texi (OPENPGP-SIGNING-KEY-ID, OPENPGP-SIGNING-KEY-URL): Rename to...
> (OPENPGP-SIGNING-KEY-ID-1, OPENPGP-SIGNING-KEY-URL-1): ... these,
> respectively.
> (OPENPGP-SIGNING-KEY-ID-2, OPENPGP-SIGNING-KEY-URL-2): New variables.
> (Binary Installation): Adjust to cover for the new key.
> (USB Stick and DVD Installation): Likewise.
> (Invoking guix refresh): Adjust accordingly.
No big deal but perhaps it would be enough to keep a single key in the
manual since we know which key is going to be used for this release.
That would avoid extra work for our translation maester, and it would
make sure we don’t endlessly accumulate keys in there as release
responsibilities rotate. WDYT?
Thanks,
Ludo’.
next parent reply other threads:[~2021-05-04 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210504033511.24042.17383@vcs0.savannah.gnu.org>
[not found] ` <20210504033513.A0CFA20D0E@vcs0.savannah.gnu.org>
2021-05-04 9:08 ` Ludovic Courtès [this message]
2021-05-04 10:57 ` 03/03: doc: Update to cover for an additional OpenPGP signing key Julien Lepiller
2021-05-04 12:17 ` Maxim Cournoyer
2021-05-04 15:29 ` Ludovic Courtès
2021-05-05 15:39 ` Maxim Cournoyer
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=874kfisw6v.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@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 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).