From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/mesa3d: fix typo in file hash
Date: Sat, 2 Jun 2018 18:15:03 +0200 [thread overview]
Message-ID: <20180602161504.8610-1-romain.naour@gmail.com> (raw)
Fix typo introduced with the bump to 18.0.4.
Commit f18ca0e7bb0e522846296139cdf0f8039d7dca1c
Signed-off-by: Romain Naour <romain.naour@gmail.com>
---
package/mesa3d/mesa3d.hash | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/mesa3d/mesa3d.hash b/package/mesa3d/mesa3d.hash
index 9b9f01703c..b6ce272c1c 100644
--- a/package/mesa3d/mesa3d.hash
+++ b/package/mesa3d/mesa3d.hash
@@ -2,7 +2,7 @@
md5 ef525adaff7f31bedd4c5134bc313da9 mesa-18.0.4.tar.xz
sha1 4bbee07d8eb42625f215f49d39a657fabdc2f29d mesa-18.0.4.tar.xz
sha256 1f3bcfe7cef0a5c20dae2b41df5d7e0a985e06be0183fa4d43b6068fcba2920f mesa-18.0.4.tar.xz
-sha512 f9a14be46c209661ceb318add1611481445d13b47e95c7a5d2a5e5ecfdd5d2c3fa9c2b16b30035bbb8d61ccc7cb65bfa6698ac8b040273e5ab045a951a67752c mesa-18.0.3.tar.xz
+sha512 f9a14be46c209661ceb318add1611481445d13b47e95c7a5d2a5e5ecfdd5d2c3fa9c2b16b30035bbb8d61ccc7cb65bfa6698ac8b040273e5ab045a951a67752c mesa-18.0.4.tar.xz
# License
sha256 630e75b4fdeb75ee2bf9e55db54dd1e3ff7353d52d9314ca8512bfd460f8e24c docs/license.html
sha256 a75ee0cec909515ff80a3ec07155b7fb0aafe8051abe1f0e45d5c4c5e2539366 docs/patents.txt
--
2.14.3
next reply other threads:[~2018-06-02 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-02 16:15 Romain Naour [this message]
2018-06-02 16:15 ` [Buildroot] [PATCH 2/2] package/{mesa3d, mesa3d-headers}: bump version to 18.1.1 Romain Naour
2018-06-02 20:27 ` Peter Korsgaard
2018-06-02 20:27 ` [Buildroot] [PATCH 1/2] package/mesa3d: fix typo in file hash Peter Korsgaard
2018-06-02 20:28 ` Thomas Petazzoni
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=20180602161504.8610-1-romain.naour@gmail.com \
--to=romain.naour@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