From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 0564584a5887b7498ae9ea638bc4799d2a6147e8
Date: Thu, 21 Mar 2024 15:45:51 +0000 [thread overview]
Message-ID: <4V0qYW15wnz2xt0@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1579 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, master has been updated
via 0564584a5887b7498ae9ea638bc4799d2a6147e8 (commit)
from 08d869d54f4903593992d7aee2ef17d79d235108 (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 0564584a5887b7498ae9ea638bc4799d2a6147e8
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Mar 21 14:56:41 2024 +0000
core185: Ship IPS ruleset sources
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/131 => core/185}/filelists/ids-ruleset-sources | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/131 => core/185}/filelists/ids-ruleset-sources (100%)
Difference in files:
diff --git a/config/rootfiles/core/185/filelists/ids-ruleset-sources b/config/rootfiles/core/185/filelists/ids-ruleset-sources
new file mode 120000
index 000000000..a226ada39
--- /dev/null
+++ b/config/rootfiles/core/185/filelists/ids-ruleset-sources
@@ -0,0 +1 @@
+../../../common/ids-ruleset-sources
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2024-03-21 15: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=4V0qYW15wnz2xt0@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