Re: Advance Notification of Suricata 7.0.9

[Michael Tremer <michael.tremer@ipfire.org>]

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