From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] pru-software-support: bump version to 5.1.0
Date: Sat, 25 Feb 2017 15:16:27 +0100 [thread overview]
Message-ID: <f75d656d-0276-7638-b4ee-637e8912a2d5@mind.be> (raw)
In-Reply-To: <20170225091424.GA3627@free.fr>
On 25-02-17 10:14, Yann E. MORIN wrote:
[snip]
> Also, it seems that gitorious is generating reproducible archives, so
> please do provide a hash. You can check if it is reproducible, the sha1
> I got here was:
> f23e64c9adf0739a7dc73a31e5d7bb798c9e5dd0 pru-software-support-v5.1.0.tar.gz
That's actually not telling much, since gitorious caches the archive for some
time. However, what you can see is that the tarball is sorted and that the
mtimes are those of the v5.1.0 commit, so indeed reproducible.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2017-02-25 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 22:44 [Buildroot] [PATCH 1/2] pru-software-support: bump version to 5.1.0 Cam Mannett
2017-02-25 9:14 ` Yann E. MORIN
2017-02-25 10:31 ` Yann E. MORIN
2017-02-25 14:16 ` Arnout Vandecappelle [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-25 8:16 Cam Mannett
2017-02-25 8:23 camden.mannett at gmail.com
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=f75d656d-0276-7638-b4ee-637e8912a2d5@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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