From: Alex Suykov <alex.suykov@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] vboot-utils: remove hash file
Date: Fri, 1 Jan 2016 16:52:44 +0200 [thread overview]
Message-ID: <20160101145244.GA29643@vostro> (raw)
In-Reply-To: <20151230235323.3f11d1ea@free-electrons.com>
Wed, Dec 30, 2015 at 11:53:23PM +0100, Thomas Petazzoni wrote:
> > 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.
Ok, got it.
Does it make sense to update the file name in .hash, or is it ok to leave it as is
since it's not used anyway? It's (version).tar.gz now but the git checkout gets saved
as vboot-utils-(version).tar.gz.
next prev parent reply other threads:[~2016-01-01 14:52 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
2016-01-01 14:52 ` Alex Suykov [this message]
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=20160101145244.GA29643@vostro \
--to=alex.suykov@gmail.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