From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 01b3a62a35a38db9d67121e66f983c0e0a38ca46
Date: Sat, 18 Jun 2022 10:39:21 +0000 [thread overview]
Message-ID: <4LQC894hW7z2xv4@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1685 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 01b3a62a35a38db9d67121e66f983c0e0a38ca46 (commit)
from be5703ef78b6244dcf06b72e6f34ab72b2e7fc55 (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 01b3a62a35a38db9d67121e66f983c0e0a38ca46
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Sat Jun 18 10:38:40 2022 +0000
u-boot: .xz != .gz
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/u-boot | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/u-boot b/lfs/u-boot
index 327548936..b1240f04c 100644
--- a/lfs/u-boot
+++ b/lfs/u-boot
@@ -41,7 +41,7 @@ ATF_VER = 2.7
# Top-level Rules
###############################################################################
-objects = $(DL_FILE) arm-trusted-firmware-$(ATF_VER).tar.gz arm-trusted-firmware-$(ATF_VER)-rk3399-binary.tar.xz
+objects = $(DL_FILE) arm-trusted-firmware-$(ATF_VER).tar.gz arm-trusted-firmware-$(ATF_VER)-rk3399-binary.tar.gz
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
arm-trusted-firmware-$(ATF_VER).tar.gz = $(DL_FROM)/arm-trusted-firmware-$(ATF_VER).tar.gz
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-06-18 10:39 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=4LQC894hW7z2xv4@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