From: Efraim Flashner <efraim@flashner.co.il>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: reproducibility
Date: Wed, 13 Jan 2016 11:15:21 +0200 [thread overview]
Message-ID: <20160113111521.516a4a50@debian-netbook> (raw)
In-Reply-To: <CAKrPhPOLVB0O3uRCP=5-c5kYYdoRXknLO8uozy8cw==xtUeznw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
On Wed, 13 Jan 2016 09:13:25 +0100
Federico Beffa <beffa@ieee.org> wrote:
> On Tue, Jan 12, 2016 at 10:37 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> [...]
> [...]
> [...]
> [...]
> [...]
> [...]
> [...]
>
> Just out of curiosity, could you provide a concrete example where the
> order is purposefully specified.
>
> Thanks,
> Fede
>
I haven't had time (since reading this) to test if the order matters or not,
but some of the openstack packages say they care about order:
https://git.openstack.org/cgit/openstack/python-keystoneclient/tree/test-requirements.txt?h=2.0.0
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-13 9:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 10:53 reproducibility Federico Beffa
2016-01-10 20:49 ` reproducibility Ludovic Courtès
2016-01-12 20:11 ` reproducibility Federico Beffa
2016-01-12 21:37 ` reproducibility Ludovic Courtès
2016-01-13 8:13 ` reproducibility Federico Beffa
2016-01-13 9:15 ` Efraim Flashner [this message]
2016-01-13 19:51 ` reproducibility Federico Beffa
2016-01-13 13:56 ` reproducibility Ludovic Courtès
2016-01-13 19:53 ` reproducibility Federico Beffa
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=20160113111521.516a4a50@debian-netbook \
--to=efraim@flashner.co.il \
--cc=beffa@ieee.org \
--cc=guix-devel@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).