From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] linuxptp: bump to the latest version
Date: Sat, 9 Sep 2017 22:08:51 +0200 [thread overview]
Message-ID: <20170909220851.56a41dc1@windsurf.lan> (raw)
In-Reply-To: <1504977449-30925-1-git-send-email-brain@jikos.cz>
Hello,
On Sat, 9 Sep 2017 19:17:29 +0200, Petr Kulhavy wrote:
> diff --git a/package/linuxptp/linuxptp.hash b/package/linuxptp/linuxptp.hash
> index ccda2d6..de28ee4 100644
> --- a/package/linuxptp/linuxptp.hash
> +++ b/package/linuxptp/linuxptp.hash
> @@ -1,2 +1,2 @@
> -# Locally computed:
> -sha256 b8190ab71a99f1dc32847f33cb301d2464d3f9e5f4c51300d55589aff42e8b3f linuxptp-97c351cafd7327fd28047580c9e2528a6f7e742b.tar.gz
> +# No hash for linuxptp, cloned from a remote repo
> +none xxx linuxptp-17c9787b1d6891636b5be9e4e5a08278b44e9a7a.tar.gz
Why are you removing the hash ?
Buildroot's mechanism to clone from a Git repository and generate a
tarball is reproducible, so we can use hashes and we do use them.
Could you fix this and send an updated version ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-09-09 20:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 17:17 [Buildroot] [PATCH 1/1] linuxptp: bump to the latest version Petr Kulhavy
2017-09-09 20:08 ` Thomas Petazzoni [this message]
2017-09-09 20:53 ` Petr Kulhavy
2017-09-10 6:04 ` Thomas Petazzoni
2017-09-10 9:24 ` Yann E. MORIN
2017-09-10 10:31 ` Petr Kulhavy
2017-09-10 18:18 ` Yann E. MORIN
2017-09-10 18:40 ` Thomas Petazzoni
2017-09-10 23:30 ` Petr Kulhavy
2017-09-11 20:04 ` Yann E. MORIN
2017-09-10 9:57 ` Petr Kulhavy
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=20170909220851.56a41dc1@windsurf.lan \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.