From: ng0 <ng0@infotropique.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: 29196@debbugs.gnu.org
Subject: bug#29196: upstreaming of reproducibility related patches
Date: Wed, 8 Nov 2017 05:12:43 +0000 [thread overview]
Message-ID: <20171108051243.2y52u2bo46oze6r3@abyayala> (raw)
In-Reply-To: <878tfim06i.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]
Jan Nieuwenhuizen transcribed 1.0K bytes:
> ng0 writes:
>
> > as I wrote in #29135, we should upstream the patches we
> > gather for reproducibility. Share with upstream what is
> > applicable to more software than just Guix included
> > definitions of the software etc.
>
> > We have no list for this so far
> > We need to share this, to avoid duplicate work elsewhere.
>
> What about the reproducible builds list?
Well, list as in a list that lists our patches, not a mailinglist ;)
> https://lists.reproducible-builds.org/listinfo/rb-general
> General discussions about reproducible builds <rb-general@lists.reproducible-builds.org>
>
> At the reproducible-builds summit last week in Berlin some work has been
> done on the topic of upstreaming patches. I think some effort has gone
> (is going?) into a email template that starts by explaining what
> reproducible-builds is, why it is important and why upstream should
> consider taking the patch.
>
> Greetings,
> janneke
>
> --
> Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
> Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
>
--
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://dist.ng0.infotropique.org/dist/keys/
WWW: https://ng0.infotropique.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-08 5:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 17:17 bug#29196: upstreaming of reproducibility related patches ng0
2017-11-07 18:08 ` Jan Nieuwenhuizen
2017-11-08 5:12 ` ng0 [this message]
2017-11-14 22:06 ` Ludovic Courtès
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=20171108051243.2y52u2bo46oze6r3@abyayala \
--to=ng0@infotropique.org \
--cc=29196@debbugs.gnu.org \
--cc=janneke@gnu.org \
/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).