From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core186, updated. 1ed2ed6310a80510304af993b68c35060731ceff
Date: Mon, 10 Jun 2024 15:37:29 +0000 [thread overview]
Message-ID: <4VybXT6t69z2xVF@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1632 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, core186 has been updated
via 1ed2ed6310a80510304af993b68c35060731ceff (commit)
from d545c338f0d14ecec48623e15efc1c28b44cbce7 (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 1ed2ed6310a80510304af993b68c35060731ceff
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Mon Jun 10 15:37:16 2024 +0000
core186: Ship ovpnmain.cgi
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/186/filelists/files | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/core/186/filelists/files b/config/rootfiles/core/186/filelists/files
index d23b4a838..0c4756337 100644
--- a/config/rootfiles/core/186/filelists/files
+++ b/config/rootfiles/core/186/filelists/files
@@ -12,6 +12,7 @@ etc/rc.d/init.d/grub-btrfsd
etc/rc.d/rc0.d/K01grub-btrfsd
etc/rc.d/rc3.d/S99grub-btrfsd
etc/rc.d/rc6.d/K01grub-btrfsd
+srv/web/ipfire/cgi-bin/ovpnmain.cgi
srv/web/ipfire/cgi-bin/vulnerabilities.cgi
usr/local/bin/ipsec-interfaces
usr/sbin/unbound-dhcp-leases-bridge
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2024-06-10 15:37 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=4VybXT6t69z2xVF@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