From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 1f200cb1c9ec0f4c9196d44f2f2c92d3403a8aae
Date: Mon, 7 Jul 2025 19:02:16 +0000 (UTC) [thread overview]
Message-ID: <4bbYWr6Ckxz2xXq@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 1f200cb1c9ec0f4c9196d44f2f2c92d3403a8aae (commit)
from 4a12f983c1eba12a337bd0cfcc592181ff6a174b (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 1f200cb1c9ec0f4c9196d44f2f2c92d3403a8aae
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Mon Jul 7 19:01:48 2025 +0000
core196: Ship man pages
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/196/filelists/files | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/core/196/filelists/files b/config/rootfiles/core/196/filelists/files
index e383a991d..a4be28a89 100644
--- a/config/rootfiles/core/196/filelists/files
+++ b/config/rootfiles/core/196/filelists/files
@@ -16,4 +16,5 @@ var/ipfire/graphs.pl
var/ipfire/header.pl
var/ipfire/ipblocklist-functions.pl
var/ipfire/langs/list
+var/ipfire/main/manualpages
var/ipfire/wireguard-functions.pl
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2025-07-07 19:02 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=4bbYWr6Ckxz2xXq@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