From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 2228871e3e8d66bf6d4857b11ca438b75c25fad2
Date: Tue, 08 Oct 2019 19:45:42 +0000 [thread overview]
Message-ID: <46nnrk5HFTz2yFP@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 2228871e3e8d66bf6d4857b11ca438b75c25fad2 (commit)
from 5b87687cb1d37d81dbc701706e40f40f2cb16348 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 2228871e3e8d66bf6d4857b11ca438b75c25fad2
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Tue Oct 8 19:44:54 2019 +0000
rust: fix md5 sums for i586 and arm
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/rust | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/rust b/lfs/rust
index 289387133..c1640ab0f 100644
--- a/lfs/rust
+++ b/lfs/rust
@@ -52,7 +52,10 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 3f84df04bd0cf0ea4668390be263945e
+$(THISAPP)-x86_64-unknown-linux-gnu.tar.gz_MD5 3f84df04bd0cf0ea4668390be263945e
+$(THISAPP)-i686-unknown-linux-gnu.tar.gz_MD5 = 29411d7420184ad51f99339b2e2cf20a
+$(THISAPP)-aarch64-unknown-linux-gnu.tar.gz_MD5 = 28f9556a3febd2d38c0ba97337d56cb8
+$(THISAPP)-arm-unknown-linux-gnueabi.tar.gz_MD5 = 970ad24c516394466e7b8ca40689ee76
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-10-08 19:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46nnrk5HFTz2yFP@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.org \
/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