From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 6fc9957e62b4f5fe9b47e9d340480b9bc33788cd
Date: Fri, 23 Aug 2024 15:29:59 +0000 [thread overview]
Message-ID: <4Wr3sg6Q5zz2xWt@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1556 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, master has been updated
via 6fc9957e62b4f5fe9b47e9d340480b9bc33788cd (commit)
from cd2069f07f611a0d0d240d2c5efe0e955763a1f1 (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 6fc9957e62b4f5fe9b47e9d340480b9bc33788cd
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Aug 23 15:29:36 2024 +0000
core-update: Append the release number to the meta file
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/core-updates | 2 ++
1 file changed, 2 insertions(+)
Difference in files:
diff --git a/lfs/core-updates b/lfs/core-updates
index a6478b5e0..81ea9a5f0 100644
--- a/lfs/core-updates
+++ b/lfs/core-updates
@@ -33,6 +33,8 @@ PAK_VER = $(CORE)
SUMMARY = IPFire Core Update $(CORE)
+META_FILENAME = meta-$(PROG)-$(CORE)
+
###############################################################################
# Top-level Rules
###############################################################################
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2024-08-23 15:29 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=4Wr3sg6Q5zz2xWt@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