From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4ZJzT00NNjz3329 for ; Fri, 21 Mar 2025 10:39:00 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) client-signature RSA-PSS (4096 bits)) (Client CN "mail01.haj.ipfire.org", Issuer "R10" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4ZJzSw3GLpz32vw for ; Fri, 21 Mar 2025 10:38:56 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4ZJzSv6q9Qz70C; Fri, 21 Mar 2025 10:38:55 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1742553536; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=UUoI/DMPmbVjrpjO5ynP8NIS0mbc1kRJ4Pgjaj7nE8E=; b=VbvoB5sX4LVQU7G2W7Iq5I295fvYWgreLR/NO7uRrVmhDDo/YBun0FBNsPdZwE8rZUdz4w eAAkUBntJtYo0MAg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1742553536; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=UUoI/DMPmbVjrpjO5ynP8NIS0mbc1kRJ4Pgjaj7nE8E=; b=U8IJffbi4n1M8dAt1rVaQwt/4dAhKF2S0IEQoF/VD8cIPewyQfGRjMDh/yVz4Zt8eeDtDD EjrBduzWxzzkZkBYtejX/WEQXagpm/E6o1sOQqz4q4J5T8Ei3Ty6vA+Onr+kEd7Qg44S8H eB0Ovy3dlfr3xoMSUFGTgp0e7wI/Z7o9Dp5IsOyYBEX0m8o9o9M3FX28tpyfvNKXi4Bv8g lUrSyi4BJtjEQ4uCXsdlobrCnFUtd3LiqpmpyodD+DyF/T+K+/+88UN0qRsDoTgzjD9wSY Haur4Ps5mlAn7pGqobj2FkGODcpDHtM3y+Eex9qVsZcH1bPa2hV4vaimRnezeg== Message-ID: Date: Fri, 21 Mar 2025 11:38:51 +0100 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Subject: Re: Advance Notification of Suricata 7.0.9 To: Matthias Fischer References: <999A6822-EBC4-44A6-970A-342641C813ED@ipfire.org> <4E7AA2E9-1A7F-45D3-B5ED-A0FE81319247@ipfire.org> <2e63b399-2b3e-4048-8897-3721add7936b@ipfire.org> <1b6934e0-1dc0-4c55-a919-240f24fac80a@ipfire.org> <8C89CA42-0F5A-49EC-92EA-7F93885AB030@ipfire.org> Content-Language: en-GB Cc: development@lists.ipfire.org From: Adolf Belka In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 wrote: >>> >>> Hi, >>> >>> On 20.03.2025 17:19, Michael Tremer wrote: >>>> Hello, >>>> >>>>> On 19 Mar 2025, at 17:33, Matthias Fischer 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 > >