From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/bird: bump version to 2.0.3
Date: Mon, 4 Feb 2019 15:41:49 +0100 [thread overview]
Message-ID: <20190204154149.6c46e8ef@windsurf> (raw)
In-Reply-To: <CAFtSRGAAkpuyg7==BY7oQ++_uWTeYaZZnA9GjrB2aNXTazQj8Q@mail.gmail.com>
Hello,
Please keep the mailing list in Cc and avoid top-posting. Thanks!
On Mon, 4 Feb 2019 15:17:44 +0100
Adrien Gallou?t <adrien@gallouet.fr> wrote:
> Hi,
> Yes (I think). We can still download the first tag of BIRD released 9yrs
> ago.
Well, that it is not really the question I was asking. My question is
whether this tarball is always *exactly* identical. As you say, it's a
tarball generated automatically. Since we store a hash of the tarball
in bird.hash, if gitlab does some subtle changes in how the tarball is
generated, the hash will change, breaking the download.
We had this issue with Github in the past.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-02-04 14:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 9:10 [Buildroot] [PATCH 1/1] package/bird: bump version to 2.0.3 Adrien Gallouët
2019-02-04 9:22 ` Baruch Siach
2019-02-04 10:02 ` [Buildroot] [PATCH v2 " Adrien Gallouët
2019-02-04 13:11 ` Thomas Petazzoni
[not found] ` <CAFtSRGAAkpuyg7==BY7oQ++_uWTeYaZZnA9GjrB2aNXTazQj8Q@mail.gmail.com>
2019-02-04 14:41 ` Thomas Petazzoni [this message]
2019-02-04 15:03 ` Adrien Gallouët
2019-02-04 15:15 ` Thomas Petazzoni
2019-02-04 15:22 ` [Buildroot] [PATCH v3 " Adrien Gallouët
2019-02-04 16:07 ` Thomas Petazzoni
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=20190204154149.6c46e8ef@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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