From: root <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 78194fc50a82f8284122bf4c83cae51ffb25b9e1
Date: Sun, 14 Sep 2025 16:36:02 +0000 (UTC) [thread overview]
Message-ID: <4cPv1G44V8z2xcq@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 78194fc50a82f8284122bf4c83cae51ffb25b9e1 (commit)
from d0d9a5d17f6f050958bf4f69b173fc24c476c5ba (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 -----------------------------------------------------------------
-----------------------------------------------------------------------
Summary of changes:
lfs/suricata-reporter | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/lfs/suricata-reporter b/lfs/suricata-reporter
index 2c592c984..e4e013e9e 100644
--- a/lfs/suricata-reporter
+++ b/lfs/suricata-reporter
@@ -24,7 +24,7 @@
include Config
-VER = 0.2
+VER = 0.3
THISAPP = suricata-reporter-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = af8a881c467898bfad94622d91733f86cfebcca848ac445c6a447e980535d0d6ea4f86be47b7e5db4a6182d0c6d21b2504aa9979aa5a113672597d00d82843e8
+$(DL_FILE)_BLAKE2 = 8e06248fadb582244b32e4bdbf68cd584e4f7048a917f4891d7c92351e5f879c5149e82d8a1c25ca14e33a954d338214b18d95bb7a92fbc87fcf9548e6dd266d
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2025-09-14 16:36 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=4cPv1G44V8z2xcq@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