public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: Matthias Fischer <matthias.fischer@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Advance Notification of Suricata 7.0.9
Date: Thu, 20 Mar 2025 16:19:41 +0000	[thread overview]
Message-ID: <B8E0587A-C0DA-42B6-A5E5-2406DB2C30D3@ipfire.org> (raw)
In-Reply-To: <bd99e729-a79a-4556-aac9-567111c7ac4f@ipfire.org>

Hello,

> On 19 Mar 2025, at 17:33, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
> 
> Hi,
> 
> One curiosity:
> 
> I've just sent the updates for 'suricata 7.0.9' and 'libhtp 0.5.50' from
> my "Devel64-1" to development@lists.ipfire.org.
> I did this as always, per 'git send-email --annotate
> --smtp-domain=devel64-1.localdomain -2'. No problems occured.
> 
> But I see these only on 'patchwork.ipfire.org' and 'git.ipfire.org'. I
> expected to get a mail on the list, as usual. But nothing happened, this
> patchset doesn't appear on the development-list.

It is here: https://lists.ipfire.org/development/20250319161626.625056-1-matthias.fischer@ipfire.org/T/#m619f245177638f2d6ef7f05a5114b596360c6cb4

What is wrong with it? Where else are you expecting it?

> 
> Did I miss something?
> 
> Best
> Matthias
> 
> On 19.03.2025 17:22, Michael Tremer wrote:
>> No problem. All merged!
>> 
>>> On 19 Mar 2025, at 16:21, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>>> 
>>> On 19.03.2025 17:16, Michael Tremer wrote:
>>>> Perfect! Thank you!
>>> 
>>> No problem.
>>>> Please don’t forget to Cc the list.
>>> 
>>> Doh!
>>> 
>>> Of course I forgot that... Next time...
>>>>> On 19 Mar 2025, at 16:10, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>>>>> 
>>>>> HI,
>>>>> 
>>>>> On 19.03.2025 16:44, Michael Tremer wrote:
>>>>>> Is anyone already on this?
>>>>> 
>>>>> Yes. ;-)
>>>>> 
>>>>> Running here. Its on its way...
>>>>> 
>>>>> Best
>>>>> Matthias
>>>>> 
>>>>>>> Begin forwarded message:
>>>>>>> 
>>>>>>> From: Jason Ish <jish@oisf.net>
>>>>>>> Subject: Advance Notification of Suricata 7.0.9
>>>>>>> Date: 17 March 2025 at 15:24:29 GMT
>>>>>>> To: Victor Julien <vjulien@oisf.net>, Jason Ish <jish@oisf.net>
>>>>>>> 
>>>>>>> Hello everyone,
>>>>>>> 
>>>>>>> On Tuesday March 18, 2025 we plan to release Suricata 7.0.9. This is a bug-fix and security release addressing a few issues.
>>>>>>> 
>>>>>>> This release will include a minor update to libhtp: 0.5.50.
>>>>>>> 
>>>>>>> For other issues addressed in this release please see:
>>>>>>> https://redmine.openinfosecfoundation.org/versions/215
>>>>>>> 
>>>>>>> Regards,
>>>>>>> The OISF Team
>>>>>>> 
>>>>>>> 
>>>>>>> To unsubscribe from this group and stop receiving emails from it, send an email to oss-advisories+unsubscribe@openinfosecfoundation.org <mailto:oss-advisories+unsubscribe@openinfosecfoundation.org>.
>>>> 
>>>> 
>>> 
>>> 
>> 
> 
> 



  reply	other threads:[~2025-03-20 16:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMYRET8wqxr2jz0ToceRsi10w1Gh7voKkwo+OQ_PZZw3VD3zKw@mail.gmail.com>
2025-03-19 15:44 ` Fwd: " Michael Tremer
     [not found]   ` <af08e30a-4706-491d-bc77-04e1e8195f42@ipfire.org>
2025-03-19 16:16     ` Michael Tremer
2025-03-19 16:21       ` Matthias Fischer
2025-03-19 16:22         ` Michael Tremer
2025-03-19 17:33           ` Matthias Fischer
2025-03-20 16:19             ` Michael Tremer [this message]
2025-03-20 17:01               ` Matthias Fischer
2025-03-20 17:42                 ` Michael Tremer
2025-03-20 17:53                   ` Adolf Belka
2025-03-20 19:32                   ` Matthias Fischer
2025-03-21 10:38                     ` Adolf Belka
2025-03-21 11:29                       ` Michael Tremer
2025-03-21 12:16                         ` Adolf Belka
2025-03-21 12:37                           ` Michael Tremer

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=B8E0587A-C0DA-42B6-A5E5-2406DB2C30D3@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    --cc=matthias.fischer@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