From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 178ed036fc2680712734569f81d1d6497e02ac66
Date: Thu, 19 Nov 2026 15:56:41 +0000 (UTC) [thread overview]
Message-ID: <4jVjkx1yFXz2xNP@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 178ed036fc2680712734569f81d1d6497e02ac66 (commit)
from 1776779ef4e4a070f91b65a7cdc81b15419511d0 (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 178ed036fc2680712734569f81d1d6497e02ac66
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Thu Nov 19 15:56:40 2026 +0000
core207: Ship the knot-resolver init script
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/207/filelists/files | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/core/207/filelists/files b/config/rootfiles/core/207/filelists/files
index d110080cb..bad5ca467 100644
--- a/config/rootfiles/core/207/filelists/files
+++ b/config/rootfiles/core/207/filelists/files
@@ -3,6 +3,7 @@ etc/httpd/conf/vhosts.d/ipfire-interface-ssl.conf
etc/rc.d/init.d/apache
etc/rc.d/init.d/firewall
etc/rc.d/init.d/functions
+etc/rc.d/init.d/knot-resolver
etc/rc.d/init.d/mountkernfs
etc/rc.d/init.d/networking/red
etc/rc.d/init.d/openvpn-n2n
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-11-19 15:56 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=4jVjkx1yFXz2xNP@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