From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. df79229e7f6f59b5799ee69a944b812a5002c0cb
Date: Sun, 31 Aug 2025 11:18:19 +0000 (UTC) [thread overview]
Message-ID: <4cF8d72T3Dz2xx8@people01.haj.ipfire.org> (raw)
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 df79229e7f6f59b5799ee69a944b812a5002c0cb (commit)
from 18b67efc6fc7414ab7a2d4865357e70c0b1da314 (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 df79229e7f6f59b5799ee69a944b812a5002c0cb
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Sun Aug 31 11:18:03 2025 +0000
fireinfo: Fix hash
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/fireinfo | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/fireinfo b/lfs/fireinfo
index b8727c778..c0b776ee0 100644
--- a/lfs/fireinfo
+++ b/lfs/fireinfo
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = f811c8acf078c6fcb27305f0a6b81429862ad9631699e50ee0e4b2e713c8e1a745ba453783422598b818da59fd4d9e96be395884a7fccd7bcda0e64c7cd8d692
+$(DL_FILE)_BLAKE2 = 3fd2159678d412befcf444f0a7fec1790cdd098e705339a56cccfa24a05b4c459239f53d73fbc39a2c10fc51147867488532eed5df151567344f2b9479c843bc
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2025-08-31 11:18 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=4cF8d72T3Dz2xx8@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