From: "André Hentschel" <nerv@dawncrow.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] am335x-pru-package: Add hash file
Date: Fri, 13 Mar 2015 00:23:02 +0100 [thread overview]
Message-ID: <55021FD6.1080104@dawncrow.de> (raw)
In-Reply-To: <87twxphlxf.fsf@dell.be.48ers.dk>
Am 12.03.2015 um 23:48 schrieb Peter Korsgaard:
>>>>>> "Andr?" == Andr? Hentschel <nerv@dawncrow.de> writes:
>
> > Signed-off-by: Andr? Hentschel <nerv@dawncrow.de>
> > ---
> > package/am335x-pru-package/am335x-pru-package.hash | 2 ++
> > 1 file changed, 2 insertions(+)
> > create mode 100644 package/am335x-pru-package/am335x-pru-package.hash
>
> > diff --git a/package/am335x-pru-package/am335x-pru-package.hash
> > b/package/am335x-pru-package/am335x-pru-package.hash
> > new file mode 100644
> > index 0000000..dcb15f6
> > --- /dev/null
> > +++ b/package/am335x-pru-package/am335x-pru-package.hash
> > @@ -0,0 +1,2 @@
> > +# Locally computed:
> > +sha256
> > e3d712c90070e2d4d2fceb798a3a916c375640f5614415bbe1b2a786f18af956
> > am335x-pru-package-506e074859891a2b350eb4f5fcb451c4961410ea.tar.gz
>
> am335x-pru-package comes from git through the github helper, and I'm not
> sure we can expect to always get the exact same hash from future
> downloads.
>
Hi,
I tried multiple times, but thinking twice you are right, maybe even adding a branch might change something.
Be free to remove this and the avrdude patch from the tracker.
prev parent reply other threads:[~2015-03-12 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 20:07 [Buildroot] [PATCH] am335x-pru-package: Add hash file André Hentschel
2015-03-12 22:48 ` Peter Korsgaard
2015-03-12 23:23 ` André Hentschel [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=55021FD6.1080104@dawncrow.de \
--to=nerv@dawncrow.de \
--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