From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libtirpc: Bump to version 1.2.5
Date: Sun, 22 Dec 2019 11:32:27 +0100 [thread overview]
Message-ID: <20191222103227.GA2948708@x230> (raw)
In-Reply-To: <20191221224315.4aa53ae3@windsurf>
Hi Thomas,
...
> > +++ b/package/libtirpc/libtirpc.hash
> > @@ -1,5 +1,4 @@
> > # From sourceforge's info on download page:
> > -sha1 d85717035cb9bd6c45557a1eb1351d3af9a69ff7 libtirpc-1.1.4.tar.bz2
> Removing just this line leaves the "From sourceforge's info on download
> page" comment a bit "alone".
> Also, Sourceforge does have the SHA1 hash for the 1.2.5 tarball, so
> instead I've re-added that line with the correct SHA1 provided by
> Sourceforge.
> Applied with this change. Thanks!
Thanks a lot for merge and sorry to keep small errors in my patches.
BTW I tried hard to search + google SHA1 hash on sourceforge, please where it is?
(for next time)
Kind regards,
Petr
next prev parent reply other threads:[~2019-12-22 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 17:45 [Buildroot] [PATCH 1/1] package/libtirpc: Bump to version 1.2.5 Petr Vorel
2019-12-21 21:43 ` Thomas Petazzoni
2019-12-22 10:32 ` Petr Vorel [this message]
2019-12-26 17:11 ` Thomas Petazzoni
2019-12-26 21:32 ` Petr Vorel
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=20191222103227.GA2948708@x230 \
--to=petr.vorel@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 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.