From: Ricardo Wurmus <rekado@elephly.net>
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 06:31:30 +0200 [thread overview]
Message-ID: <87fucuhisd.fsf@elephly.net> (raw)
In-Reply-To: <2b3fcfaa.1722b.15ddc6072b0.Coremail.zren@dlut.edu.cn>
Hi Ren,
> 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:
Thank you for doing this important work!
> 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?
Either mailing list is fine for these patches. I’ll take a look at them
soon.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-08-14 4:31 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 [this message]
2017-08-14 20:01 ` Leo Famulari
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=87fucuhisd.fsf@elephly.net \
--to=rekado@elephly.net \
--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).