Fwd: Advance Notification of Suricata 7.0.9

Fwd: Advance Notification of Suricata 7.0.9

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 841 bytes --]

Is anyone already on this?

> 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>.


[-- Attachment #2: Type: text/html, Size: 4851 bytes --]

Re: Advance Notification of Suricata 7.0.9

[Michael Tremer]

Perfect! Thank you!

Please don’t forget to Cc the list.

> 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>.

Re: Advance Notification of Suricata 7.0.9

[Matthias Fischer]

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>.
> 
> 

Re: Advance Notification of Suricata 7.0.9

[Michael Tremer]

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>.
>> 
>> 
> 
> 

Re: Advance Notification of Suricata 7.0.9

[Matthias Fischer]

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.

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>.
>>> 
>>> 
>> 
>> 
> 

Re: Advance Notification of Suricata 7.0.9

[Michael Tremer]

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>.
>>>> 
>>>> 
>>> 
>>> 
>> 
> 
> 

Re: Advance Notification of Suricata 7.0.9

[Matthias Fischer]

Hi,

On 20.03.2025 17:19, Michael Tremer wrote:
> 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?

As I wrote: I expected to receive a *mail* with a subject like "[Patch
1/2] libhtp: Update ..." as usual and as seen on your link above. But
there was no mail, so I wasn't sure if the patch had arrived. It had, as
I saw in patchwork and git, but only there, not in my
imap-development-inbox in Thunderbird. Thats all... ;-)

I'll soon send a patch for 'bind 9.20.7' and see what happens...

Best
Matthias

> ...

Re: Advance Notification of Suricata 7.0.9

[Michael Tremer]

Hello,

> On 20 Mar 2025, at 17:01, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
> 
> Hi,
> 
> On 20.03.2025 17:19, Michael Tremer wrote:
>> 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?
> 
> As I wrote: I expected to receive a *mail* with a subject like "[Patch
> 1/2] libhtp: Update ..." as usual and as seen on your link above. But
> there was no mail, so I wasn't sure if the patch had arrived. It had, as
> I saw in patchwork and git, but only there, not in my
> imap-development-inbox in Thunderbird. Thats all... ;-)

Ah, yeah, the new mailing list does not send you a copy of your own email any more…

I don’t think we can change this on a per-user basis, but we can globally.

Is this breaking anything for you or just unexpected?

-Michael

> 
> I'll soon send a patch for 'bind 9.20.7' and see what happens...
> 
> Best
> Matthias
> 
>> ...

Re: Advance Notification of Suricata 7.0.9

[Adolf Belka]

On 20/03/2025 18:42, Michael Tremer wrote:
> Hello,
> 
>> On 20 Mar 2025, at 17:01, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>>
>> Hi,
>>
>> On 20.03.2025 17:19, Michael Tremer wrote:
>>> 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?
>>
>> As I wrote: I expected to receive a *mail* with a subject like "[Patch
>> 1/2] libhtp: Update ..." as usual and as seen on your link above. But
>> there was no mail, so I wasn't sure if the patch had arrived. It had, as
>> I saw in patchwork and git, but only there, not in my
>> imap-development-inbox in Thunderbird. Thats all... ;-)
> 
> Ah, yeah, the new mailing list does not send you a copy of your own email any more…

With all the patches I have recently sent in, I got an email copy of all of them, the same as I got before. I didn't change anything in my git setup when the mailing list stuff changed. It just worked for me.

Regards,

Adolf.

> 
> I don’t think we can change this on a per-user basis, but we can globally.
> 
> Is this breaking anything for you or just unexpected?
> 
> -Michael
> 
>>
>> I'll soon send a patch for 'bind 9.20.7' and see what happens...
>>
>> Best
>> Matthias
>>
>>> ...
> 
> 
> 

Re: Advance Notification of Suricata 7.0.9

[Matthias Fischer]

Hi,

On 20.03.2025 18:42, Michael Tremer wrote:
> Hello,
> 
>> On 20 Mar 2025, at 17:01, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>> 
>> Hi,
>> 
>> On 20.03.2025 17:19, Michael Tremer wrote:
>>> 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?
>> 
>> As I wrote: I expected to receive a *mail* with a subject like "[Patch
>> 1/2] libhtp: Update ..." as usual and as seen on your link above. But
>> there was no mail, so I wasn't sure if the patch had arrived. It had, as
>> I saw in patchwork and git, but only there, not in my
>> imap-development-inbox in Thunderbird. Thats all... ;-)
> 
> Ah, yeah, the new mailing list does not send you a copy of your own email any more…
> 
> I don’t think we can change this on a per-user basis, but we can globally.
> 
> Is this breaking anything for you or just unexpected?
> 

No, nothing breaked - it was just unexpected.

And the mail copy was practical, because you don't have to check if the
patch has arrived.

Then again, why is it still working for Adolf? ;-)

Best
Matthias

Re: Advance Notification of Suricata 7.0.9

[Adolf Belka]

Hi Matthias,

On 20/03/2025 20:32, Matthias Fischer wrote:
> Hi,
> 
> On 20.03.2025 18:42, Michael Tremer wrote:
>> Hello,
>>
>>> On 20 Mar 2025, at 17:01, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>>>
>>> Hi,
>>>
>>> On 20.03.2025 17:19, Michael Tremer wrote:
>>>> 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.

A difference I see between us is that I just use git send-email "path to patch file".

I have the sendemail git commands set up in my .gitconfig file.

What I notice is that the default behaviour of git send-email is to take any email addresses it finds in the commit message and adds them to the cc list removing any duplicates.

As I am listed in the Signed-by line then I end up in the From and CC list. Therefore I get an email with each patch I submit.
This cc mail is separate from the dev list mail that the patch is sent to. I have never received an email via the mail list manager.

I know this because when there was the problem that the old mail list manager was not running for a while, I received emails for each patch I sent, via the IPFire mail server system and my cc email address, but none of the patches got into the mailing list archive or patchwork, until the mail list manager software was restarted.

So it might be that we have different .gitconfig settings and different command line options for git send-email, mine being just what the default is set to in Arch Linux.

Regards,

Adolf.

>>>>>
>>>>> 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?
>>>
>>> As I wrote: I expected to receive a *mail* with a subject like "[Patch
>>> 1/2] libhtp: Update ..." as usual and as seen on your link above. But
>>> there was no mail, so I wasn't sure if the patch had arrived. It had, as
>>> I saw in patchwork and git, but only there, not in my
>>> imap-development-inbox in Thunderbird. Thats all... ;-)
>>
>> Ah, yeah, the new mailing list does not send you a copy of your own email any more…
>>
>> I don’t think we can change this on a per-user basis, but we can globally.
>>
>> Is this breaking anything for you or just unexpected?
>>
> 
> No, nothing breaked - it was just unexpected.
> 
> And the mail copy was practical, because you don't have to check if the
> patch has arrived.
> 
> Then again, why is it still working for Adolf? ;-)
> 
> Best
> Matthias
> 
> 

Re: Advance Notification of Suricata 7.0.9

[Michael Tremer]

Hello,

> On 21 Mar 2025, at 10:38, Adolf Belka <adolf.belka@ipfire.org> wrote:
> 
> Hi Matthias,
> 
> On 20/03/2025 20:32, Matthias Fischer wrote:
>> Hi,
>> On 20.03.2025 18:42, Michael Tremer wrote:
>>> Hello,
>>> 
>>>> On 20 Mar 2025, at 17:01, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> On 20.03.2025 17:19, Michael Tremer wrote:
>>>>> 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.
> 
> A difference I see between us is that I just use git send-email "path to patch file".
> 
> I have the sendemail git commands set up in my .gitconfig file.
> 
> What I notice is that the default behaviour of git send-email is to take any email addresses it finds in the commit message and adds them to the cc list removing any duplicates.

Ah yes, that obviously works.

I personally don’t like to receive a copy of my own email, because my email client already has it. If I send it from git send-email I don’t have it in my inbox, but I have never missed it.

> As I am listed in the Signed-by line then I end up in the From and CC list. Therefore I get an email with each patch I submit.
> This cc mail is separate from the dev list mail that the patch is sent to. I have never received an email via the mail list manager.
> 
> I know this because when there was the problem that the old mail list manager was not running for a while, I received emails for each patch I sent, via the IPFire mail server system and my cc email address, but none of the patches got into the mailing list archive or patchwork, until the mail list manager software was restarted.

Hopefully we are at a point now where we can really rely on all emails making it to the right places. I have a much better feeling with mlmmj now.

> So it might be that we have different .gitconfig settings and different command line options for git send-email, mine being just what the default is set to in Arch Linux.

Would you like to add this to the wiki? Is this interesting for other people, too?

-Michael

> Regards,
> 
> Adolf.
> 
>>>>>> 
>>>>>> 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?
>>>> 
>>>> As I wrote: I expected to receive a *mail* with a subject like "[Patch
>>>> 1/2] libhtp: Update ..." as usual and as seen on your link above. But
>>>> there was no mail, so I wasn't sure if the patch had arrived. It had, as
>>>> I saw in patchwork and git, but only there, not in my
>>>> imap-development-inbox in Thunderbird. Thats all... ;-)
>>> 
>>> Ah, yeah, the new mailing list does not send you a copy of your own email any more…
>>> 
>>> I don’t think we can change this on a per-user basis, but we can globally.
>>> 
>>> Is this breaking anything for you or just unexpected?
>>> 
>> No, nothing breaked - it was just unexpected.
>> And the mail copy was practical, because you don't have to check if the
>> patch has arrived.
>> Then again, why is it still working for Adolf? ;-)
>> Best
>> Matthias

Re: Advance Notification of Suricata 7.0.9

[Adolf Belka]

Hi Michael,

On 21/03/2025 12:29, Michael Tremer wrote:
> Hello,
> 
>> On 21 Mar 2025, at 10:38, Adolf Belka <adolf.belka@ipfire.org> wrote:
>>
>> Hi Matthias,
>>
>> On 20/03/2025 20:32, Matthias Fischer wrote:
>>> Hi,
>>> On 20.03.2025 18:42, Michael Tremer wrote:
>>>> Hello,
>>>>
>>>>> On 20 Mar 2025, at 17:01, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> On 20.03.2025 17:19, Michael Tremer wrote:
>>>>>> 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.
>>
>> A difference I see between us is that I just use git send-email "path to patch file".
>>
>> I have the sendemail git commands set up in my .gitconfig file.
>>
>> What I notice is that the default behaviour of git send-email is to take any email addresses it finds in the commit message and adds them to the cc list removing any duplicates.
> 
> Ah yes, that obviously works.
> 
> I personally don’t like to receive a copy of my own email, because my email client already has it. If I send it from git send-email I don’t have it in my inbox, but I have never missed it.

My email client is Thunderbird and that doesn't get any of the mails that I send via git send-email.

> 
>> As I am listed in the Signed-by line then I end up in the From and CC list. Therefore I get an email with each patch I submit.
>> This cc mail is separate from the dev list mail that the patch is sent to. I have never received an email via the mail list manager.
>>
>> I know this because when there was the problem that the old mail list manager was not running for a while, I received emails for each patch I sent, via the IPFire mail server system and my cc email address, but none of the patches got into the mailing list archive or patchwork, until the mail list manager software was restarted.
> 
> Hopefully we are at a point now where we can really rely on all emails making it to the right places. I have a much better feeling with mlmmj now.

I definitely think we are much better placed now.

> 
>> So it might be that we have different .gitconfig settings and different command line options for git send-email, mine being just what the default is set to in Arch Linux.
> 
> Would you like to add this to the wiki? Is this interesting for other people, too?

I will do that. Might raise it as a bug report so I don't forget it.

I have occasionally spotted things in old post threads where I said I was going to do something but it was never put in a bug report and I just forgot about it until I happened to accidentally see it again.

Regards,

Adolf.

> 
> -Michael
> 
>> Regards,
>>
>> Adolf.
>>
>>>>>>>
>>>>>>> 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?
>>>>>
>>>>> As I wrote: I expected to receive a *mail* with a subject like "[Patch
>>>>> 1/2] libhtp: Update ..." as usual and as seen on your link above. But
>>>>> there was no mail, so I wasn't sure if the patch had arrived. It had, as
>>>>> I saw in patchwork and git, but only there, not in my
>>>>> imap-development-inbox in Thunderbird. Thats all... ;-)
>>>>
>>>> Ah, yeah, the new mailing list does not send you a copy of your own email any more…
>>>>
>>>> I don’t think we can change this on a per-user basis, but we can globally.
>>>>
>>>> Is this breaking anything for you or just unexpected?
>>>>
>>> No, nothing breaked - it was just unexpected.
>>> And the mail copy was practical, because you don't have to check if the
>>> patch has arrived.
>>> Then again, why is it still working for Adolf? ;-)
>>> Best
>>> Matthias
> 
> 

Re: Advance Notification of Suricata 7.0.9

[Michael Tremer]

Hello,

> On 21 Mar 2025, at 12:16, Adolf Belka <adolf.belka@ipfire.org> wrote:
> 
> Hi Michael,
> 
> On 21/03/2025 12:29, Michael Tremer wrote:
>> Hello,
>>> On 21 Mar 2025, at 10:38, Adolf Belka <adolf.belka@ipfire.org> wrote:
>>> 
>>> Hi Matthias,
>>> 
>>> On 20/03/2025 20:32, Matthias Fischer wrote:
>>>> Hi,
>>>> On 20.03.2025 18:42, Michael Tremer wrote:
>>>>> Hello,
>>>>> 
>>>>>> On 20 Mar 2025, at 17:01, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>>>>>> 
>>>>>> Hi,
>>>>>> 
>>>>>> On 20.03.2025 17:19, Michael Tremer wrote:
>>>>>>> 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.
>>> 
>>> A difference I see between us is that I just use git send-email "path to patch file".
>>> 
>>> I have the sendemail git commands set up in my .gitconfig file.
>>> 
>>> What I notice is that the default behaviour of git send-email is to take any email addresses it finds in the commit message and adds them to the cc list removing any duplicates.
>> Ah yes, that obviously works.
>> I personally don’t like to receive a copy of my own email, because my email client already has it. If I send it from git send-email I don’t have it in my inbox, but I have never missed it.
> 
> My email client is Thunderbird and that doesn't get any of the mails that I send via git send-email.

Oh I thought you were permanently Cc-ing yourself. That way, you would always get a copy.

>>> As I am listed in the Signed-by line then I end up in the From and CC list. Therefore I get an email with each patch I submit.
>>> This cc mail is separate from the dev list mail that the patch is sent to. I have never received an email via the mail list manager.
>>> 
>>> I know this because when there was the problem that the old mail list manager was not running for a while, I received emails for each patch I sent, via the IPFire mail server system and my cc email address, but none of the patches got into the mailing list archive or patchwork, until the mail list manager software was restarted.
>> Hopefully we are at a point now where we can really rely on all emails making it to the right places. I have a much better feeling with mlmmj now.
> 
> I definitely think we are much better placed now.
> 
>>> So it might be that we have different .gitconfig settings and different command line options for git send-email, mine being just what the default is set to in Arch Linux.
>> Would you like to add this to the wiki? Is this interesting for other people, too?
> 
> I will do that. Might raise it as a bug report so I don't forget it.
> 
> I have occasionally spotted things in old post threads where I said I was going to do something but it was never put in a bug report and I just forgot about it until I happened to accidentally see it again.

Same. It happens, but feel free to fill the bug tracker. It has plenty of space for lots more tickets.

-Michael

> Regards,
> 
> Adolf.
> 
>> -Michael
>>> Regards,
>>> 
>>> Adolf.
>>> 
>>>>>>>> 
>>>>>>>> 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?
>>>>>> 
>>>>>> As I wrote: I expected to receive a *mail* with a subject like "[Patch
>>>>>> 1/2] libhtp: Update ..." as usual and as seen on your link above. But
>>>>>> there was no mail, so I wasn't sure if the patch had arrived. It had, as
>>>>>> I saw in patchwork and git, but only there, not in my
>>>>>> imap-development-inbox in Thunderbird. Thats all... ;-)
>>>>> 
>>>>> Ah, yeah, the new mailing list does not send you a copy of your own email any more…
>>>>> 
>>>>> I don’t think we can change this on a per-user basis, but we can globally.
>>>>> 
>>>>> Is this breaking anything for you or just unexpected?
>>>>> 
>>>> No, nothing breaked - it was just unexpected.
>>>> And the mail copy was practical, because you don't have to check if the
>>>> patch has arrived.
>>>> Then again, why is it still working for Adolf? ;-)
>>>> Best
>>>> Matthias