From: Leo Famulari <leo@famulari.name>
To: "Z. Ren" <zren@dlut.edu.cn>
Cc: help-guix@gnu.org
Subject: Re: Where to submit/discuss reproducible-related patches?
Date: Mon, 14 Aug 2017 16:01:50 -0400 [thread overview]
Message-ID: <20170814200150.GA10385@jasmine.lan> (raw)
In-Reply-To: <2b3fcfaa.1722b.15ddc6072b0.Coremail.zren@dlut.edu.cn>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
On Mon, Aug 14, 2017 at 12:14:54AM +0800, Z. Ren wrote:
> Hello Guix,
>
> I'm playing around with the reproducible issues recently. After some
> investigation work, I tried fixing the unreproducible issues for three
> packages, and sent the patches to the guix-patches (mentioned in the
> guix manual) mailing list:
>
> http://lists.gnu.org/archive/html/guix-patches/2017-08/msg00182.html
> http://lists.gnu.org/archive/html/guix-patches/2017-08/msg00183.html
> http://lists.gnu.org/archive/html/guix-patches/2017-08/msg00184.html
>
> However, after the submission, I did some search, and noticed that
> most reproducible-related bugs/patches seem to be posted to the
> bug-guix mailing list. I'm wondering if I posted the patches to the
> wrong place? If so, shall I post the patches to bug-guix? Sorry that
> I'm new to Guix. Hope to hear any suggestions and comments.
I agree with Ricardo: thank you for sending these patches!
We should apply them as appropriate, but we should also try to get them
upstream, because it's relatively inefficient for each distro to handle
them separately.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-08-14 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-13 16:14 Where to submit/discuss reproducible-related patches? Z. Ren
2017-08-14 4:31 ` Ricardo Wurmus
2017-08-14 20:01 ` Leo Famulari [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170814200150.GA10385@jasmine.lan \
--to=leo@famulari.name \
--cc=help-guix@gnu.org \
--cc=zren@dlut.edu.cn \
/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).