From: Danny Milosavljevic <dannym@scratchpost.org>
To: Nikolai Merinov <nikolai.merinov@member.fsf.org>
Cc: 33066@debbugs.gnu.org
Subject: [bug#33066] [PATCHv3] gnu: rust: workaround rust 1.25-27 reproducibility issues
Date: Fri, 26 Oct 2018 18:12:34 +0200 [thread overview]
Message-ID: <20181026181234.62729a14@scratchpost.org> (raw)
In-Reply-To: <877ei5lyvh.fsf@member.fsf.org>
[-- Attachment #1: Type: text/plain, Size: 365 bytes --]
Hi Nikolai,
On Fri, 26 Oct 2018 16:40:34 +0500
Nikolai Merinov <nikolai.merinov@member.fsf.org> wrote:
> Unfortunately I'll be not able to return to this reproducibility
> investigation for a while. So currently I can suggest to merge changes
> without rust 1.29 to have reproducible chain from 1.23 to 1.28.
I did so now.
Thanks for the hard work!
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-10-26 16:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 18:00 [bug#33066] [PATCH 0/2] Workaround rust reproducibility issues Nikolai Merinov
2018-10-15 21:32 ` [bug#33066] [PATCH 1/2] gnu: rust: workaround rust 1.25-27 " Nikolai Merinov
2018-10-17 11:14 ` Danny Milosavljevic
2018-10-19 19:44 ` Nikolai Merinov
2018-10-19 20:58 ` [bug#33066] [PATCHv3] " Nikolai Merinov
2018-10-21 7:28 ` Nikolai Merinov
2018-10-24 19:43 ` Danny Milosavljevic
2018-10-25 5:44 ` Danny Milosavljevic
2018-10-26 11:40 ` Nikolai Merinov
2018-10-26 16:12 ` Danny Milosavljevic [this message]
2021-02-05 15:00 ` bug#33066: [PATCH 0/2] Workaround rust " Maxim Cournoyer
2018-10-15 21:37 ` [bug#33066] [PATCH 2/2] gnu: rust: add rust 1.28 and rust 1.29 packages Nikolai Merinov
2018-10-17 11:15 ` Danny Milosavljevic
2018-10-17 14:14 ` Joe Hillenbrand
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181026181234.62729a14@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=33066@debbugs.gnu.org \
--cc=nikolai.merinov@member.fsf.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.