From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 978e8029150ae57cb1ec0326a7e341a50c850f49
Date: Fri, 07 Nov 2025 11:45:36 +0000 (UTC) [thread overview]
Message-ID: <4d2y1D56qmz2xx8@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 978e8029150ae57cb1ec0326a7e341a50c850f49 (commit)
from 57d92ffc448a5dcdd810b77d1c332f8e4ef104e6 (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 978e8029150ae57cb1ec0326a7e341a50c850f49
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Fri Nov 7 11:45:22 2025 +0000
core199: Ship ntp because of OpenSSL update
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/100 => core/199}/filelists/ntp | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/100 => core/199}/filelists/ntp (100%)
Difference in files:
diff --git a/config/rootfiles/core/199/filelists/ntp b/config/rootfiles/core/199/filelists/ntp
new file mode 120000
index 000000000..7542d86cb
--- /dev/null
+++ b/config/rootfiles/core/199/filelists/ntp
@@ -0,0 +1 @@
+../../../common/ntp
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2025-11-07 11: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=4d2y1D56qmz2xx8@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