From: Rob Browning <rlb@defaultvalue.org>
To: Ricardo Wurmus <rekado@elephly.net>, guile-devel@gnu.org
Cc: "Andy Wingo" <wingo@igalia.com>, "Mark H Weaver" <mhw@netris.org>,
"Ludovic Courtès" <ludo@gnu.org>
Subject: Re: Distributed verification of release tarballs using Guix? (was Re: Releasing 2.2.5?)
Date: Thu, 25 Jul 2019 10:26:40 -0500 [thread overview]
Message-ID: <87y30mkudr.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <87blxia3sw.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> Ludovic and other folks in the Guile and Guix communities are
> participating in the reproducible builds effort since the first summit.
Oh, excellent. (Now that you mention it, I think I remember seeing Guix
mentioned, and had just forgotten.)
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
prev parent reply other threads:[~2019-07-25 15:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 8:44 Releasing 2.2.5? Ludovic Courtès
2019-06-06 8:56 ` Nala Ginrut
2019-06-06 16:48 ` Mike Gran
2019-06-16 7:48 ` Distributed verification of release tarballs using Guix? (was Re: Releasing 2.2.5?) Mark H Weaver
2019-06-16 21:23 ` Ludovic Courtès
2019-06-16 22:17 ` Mark H Weaver
2019-06-17 8:44 ` Ludovic Courtès
2019-06-19 2:48 ` Mark H Weaver
2019-06-20 10:54 ` Ludovic Courtès
2019-06-20 21:53 ` Mark H Weaver
2019-06-21 9:27 ` Neil Jerram
2019-07-25 4:15 ` Rob Browning
2019-07-25 8:58 ` Ricardo Wurmus
2019-07-25 15:26 ` Rob Browning [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y30mkudr.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=mhw@netris.org \
--cc=rekado@elephly.net \
--cc=wingo@igalia.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.
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).