From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] vboot-utils: remove hash file
Date: Wed, 30 Dec 2015 23:53:23 +0100 [thread overview]
Message-ID: <20151230235323.3f11d1ea@free-electrons.com> (raw)
In-Reply-To: <56845669.3050005@mind.be>
Arnout,
On Wed, 30 Dec 2015 23:10:49 +0100, Arnout Vandecappelle wrote:
> IIRC the main reason why we didn't fully go for the "add hash files for all
> packages" approach was that we would need to add an empty hash file for about
> 300 packages. But then we discovered that github could have hash files, but we
> weren't entirely sure yet if that was really true.
>
> So I think now we can safely conclude that a hash file should be added for all
> packages, even if it just contains 'none' hashes. It is definitely an advantage
> to be able to distinguish packages that should still get a hash from packages of
Agreed.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-30 22:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 14:05 [Buildroot] [PATCH 0/3] vboot-utils fixes Alex Suykov
2015-12-30 14:05 ` [Buildroot] [PATCH 1/3] vboot-utils: MTD_CHAR_MAJOR definition Alex Suykov
2015-12-30 14:58 ` Thomas Petazzoni
2015-12-30 14:05 ` [Buildroot] [PATCH 2/3] vboot-utils: ssize_t needs unistd.h Alex Suykov
2015-12-30 14:58 ` Thomas Petazzoni
2015-12-30 14:06 ` [Buildroot] [PATCH 3/3] vboot-utils: remove hash file Alex Suykov
2015-12-30 15:00 ` Thomas Petazzoni
2015-12-30 21:41 ` Arnout Vandecappelle
2015-12-30 21:53 ` Thomas Petazzoni
2015-12-30 22:10 ` Arnout Vandecappelle
2015-12-30 22:53 ` Thomas Petazzoni [this message]
2016-01-01 14:52 ` Alex Suykov
2016-01-01 21:52 ` Yann E. MORIN
2016-01-01 19:45 ` Peter Korsgaard
2016-01-02 6:17 ` [Buildroot] [PATCH 0/3] vboot-utils fixes Mike Frysinger
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=20151230235323.3f11d1ea@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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