public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Advance Notification of Suricata 7.0.9
Date: Thu, 20 Mar 2025 20:32:43 +0100	[thread overview]
Message-ID: <e2fb9d05-db1f-4401-b0af-2d6f8d0b462a@ipfire.org> (raw)
In-Reply-To: <8C89CA42-0F5A-49EC-92EA-7F93885AB030@ipfire.org>

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



  parent reply	other threads:[~2025-03-20 19:32 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
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 [this message]
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=e2fb9d05-db1f-4401-b0af-2d6f8d0b462a@ipfire.org \
    --to=matthias.fischer@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