From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Bugs for Stefan to have a look at.
Date: Mon, 06 Mar 2023 22:19:29 +0100 [thread overview]
Message-ID: <8c1f1b38-01ae-4fb3-58ff-996ddb5cbe9b@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 312 bytes --]
Hi Stefan,
Sorry for forgetting about this from the last video conf call.
The following are the bugs I had a look at and couldn't figure out how
to deal with and so thought would benefit from your attention.
12979 ip block list
12960 suricata
12948 suricata
Regards,
Adolf.
--
Sent from my laptop
reply other threads:[~2023-03-06 21:19 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=8c1f1b38-01ae-4fb3-58ff-996ddb5cbe9b@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@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