From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] support/download: be more aggressive on missing hashes (branch yem/dl-hash)
Date: Tue, 17 Mar 2015 10:15:43 +0100 [thread overview]
Message-ID: <20150317091543.GA4729@free.fr> (raw)
In-Reply-To: <cover.1426545571.git.yann.morin.1998@free.fr>
All,
On 2015-03-16 23:41 +0100, Yann E. MORIN spake thusly:
> This series makes hashes mandatory when a .hash file exists.
Forget this series: it is broken for git downloads, and potentially for
all non-tarball downloads as well...
Sorry...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2015-03-17 9:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 22:41 [Buildroot] [PATCH 0/3] support/download: be more aggressive on missing hashes (branch yem/dl-hash) Yann E. MORIN
2015-03-16 22:41 ` [Buildroot] [PATCH 1/3] support/download: return different exit codes for different failures Yann E. MORIN
2015-03-16 22:58 ` Samuel Martin
2015-03-16 22:41 ` [Buildroot] [PATCH 2/3] support/download: properly catch missing hashes Yann E. MORIN
2015-03-16 22:41 ` [Buildroot] [PATCH 3/3] support/download: always fail when there's no hash Yann E. MORIN
2015-03-16 23:04 ` Samuel Martin
2015-03-18 23:15 ` Arnout Vandecappelle
2015-03-19 0:06 ` Yann E. MORIN
2015-03-17 9:15 ` Yann E. MORIN [this message]
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=20150317091543.GA4729@free.fr \
--to=yann.morin.1998@free.fr \
--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