From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. e3fc6db16b1cd81796f41d367697cdbeafa73aa0
Date: Mon, 20 Apr 2026 10:27:16 +0000 (UTC) [thread overview]
Message-ID: <4fzhW86kfYz2xZ2@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, master has been updated
via e3fc6db16b1cd81796f41d367697cdbeafa73aa0 (commit)
from a7f578e949a385e79f1b39f5ac19d7fea32f4bed (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 e3fc6db16b1cd81796f41d367697cdbeafa73aa0
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Mon Apr 20 10:27:01 2026 +0000
core201: Ship network-functions.pl
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/201/filelists/files | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/core/201/filelists/files b/config/rootfiles/core/201/filelists/files
index ef9e832d2..552e85feb 100644
--- a/config/rootfiles/core/201/filelists/files
+++ b/config/rootfiles/core/201/filelists/files
@@ -13,4 +13,5 @@ usr/bin/suricata-report-cron
var/ipfire/dns/dnsbl.json
var/ipfire/ids-functions.pl
var/ipfire/menu.d/50-firewall.menu
+var/ipfire/network-functions.pl
var/ipfire/urlfilter/bin/autoupdate.pl
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-04-20 10:27 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=4fzhW86kfYz2xZ2@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