public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. c6e906909970646658beaeb6aa62db665cb37412
Date: Wed, 24 Nov 2021 19:09:45 +0000	[thread overview]
Message-ID: <4HzrD92VRJz2xvS@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2193 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, next has been updated
       via  c6e906909970646658beaeb6aa62db665cb37412 (commit)
      from  063906ebc232ec0c3d95b29fdb3b68c6f4e980c8 (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 c6e906909970646658beaeb6aa62db665cb37412
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Wed Nov 24 19:09:01 2021 +0000

    suricata: rootfile update
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 config/rootfiles/common/suricata | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

Difference in files:
diff --git a/config/rootfiles/common/suricata b/config/rootfiles/common/suricata
index 7c512b033..ff31ec7d2 100644
--- a/config/rootfiles/common/suricata
+++ b/config/rootfiles/common/suricata
@@ -17,7 +17,7 @@ usr/bin/suricata
 #usr/share/man/man1/suricatactl-filestore.1
 #usr/share/man/man1/suricatactl.1
 #usr/share/man/man1/suricatasc.1
-usr/share/suricata/
+usr/share/suricata
 #usr/share/suricata/classification.config
 #usr/share/suricata/reference.config
 #usr/share/suricata/rules
@@ -27,12 +27,10 @@ usr/share/suricata/
 #usr/share/suricata/rules/dnp3-events.rules
 #usr/share/suricata/rules/dns-events.rules
 #usr/share/suricata/rules/files.rules
-#usr/share/suricata/rules/http2-events.rules
 #usr/share/suricata/rules/http-events.rules
 #usr/share/suricata/rules/ipsec-events.rules
 #usr/share/suricata/rules/kerberos-events.rules
 #usr/share/suricata/rules/modbus-events.rules
-#usr/share/suricata/rules/mqtt-events.rules
 #usr/share/suricata/rules/nfs-events.rules
 #usr/share/suricata/rules/ntp-events.rules
 #usr/share/suricata/rules/smb-events.rules


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2021-11-24 19:09 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=4HzrD92VRJz2xvS@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