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 4ZK0bM12kFz3328 for ; Fri, 21 Mar 2025 11:29:35 +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) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R10" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4ZK0bH3w6Hz32vw for ; Fri, 21 Mar 2025 11:29:31 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4ZK0bG5Ww1z6xG; Fri, 21 Mar 2025 11:29:30 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1742556570; 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=Ql6Nm+LYEsb3uKx+5IUrZMveZbQ1uH/MFD34MyFLh5s=; b=TItV47ArxX+zY1iaE8rjGQk5Anuf3Vof8PVaGLq/7KEgSif8r7+2os+hkdBrcz/ep93B+a +Crw/eOJ+XL0nlAw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1742556570; 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=Ql6Nm+LYEsb3uKx+5IUrZMveZbQ1uH/MFD34MyFLh5s=; b=vV+hbj+rcJtUlCCrgRp8cCgqOJNLBCSxzO+z7fstG/Q20jZASmffdODSoHE9JvdKcgO8Cy oMfKba7a3RPHLQVNNFchPQA7zbeO4kp3A7y5+Iv1Munheb0XP5T1vI00j1byWyyfg8ZWiU Uwgb8ezR7AfSe0TQA5Fu327Rb3AImkFGMciJTg7IPv5cpTgtwWYF8vkllZ7qeSYg/urgSd D9FMzMp2jW8NFJ+dVVCzQuowBGDpBDFCC7Fcgg9LEAvPD5NH4TAjIalVtIAtJ2K5Qbs7fH E3MIF57Zht62q8JPaqsywGxqTNxQ0NST9rWuaopiOj26XwrvEo4AfcVv8/or8A== Content-Type: text/plain; charset=utf-8 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 From: Michael Tremer In-Reply-To: Date: Fri, 21 Mar 2025 11:29:30 +0000 Cc: Matthias Fischer , development@lists.ipfire.org Content-Transfer-Encoding: quoted-printable Message-Id: <4BE88691-511D-41EB-9AD9-C133854B5561@ipfire.org> 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> To: Adolf Belka Hello, > On 21 Mar 2025, at 10:38, Adolf Belka wrote: >=20 > Hi Matthias, >=20 > On 20/03/2025 20:32, Matthias Fischer wrote: >> Hi, >> On 20.03.2025 18:42, Michael Tremer wrote: >>> Hello, >>>=20 >>>> On 20 Mar 2025, at 17:01, Matthias Fischer = wrote: >>>>=20 >>>> Hi, >>>>=20 >>>> On 20.03.2025 17:19, Michael Tremer wrote: >>>>> Hello, >>>>>=20 >>>>>> On 19 Mar 2025, at 17:33, Matthias Fischer = wrote: >>>>>>=20 >>>>>> Hi, >>>>>>=20 >>>>>> One curiosity: >>>>>>=20 >>>>>> 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=3Ddevel64-1.localdomain -2'. No problems occured. >=20 > A difference I see between us is that I just use git send-email "path = to patch file". >=20 > I have the sendemail git commands set up in my .gitconfig file. >=20 > 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=E2=80=99t 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=E2=80=99t 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 =46rom 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. >=20 > 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, >=20 > Adolf. >=20 >>>>>>=20 >>>>>> 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. >>>>>=20 >>>>> It is here: = https://lists.ipfire.org/development/20250319161626.625056-1-matthias.fisc= her@ipfire.org/T/#m619f245177638f2d6ef7f05a5114b596360c6cb4 >>>>>=20 >>>>> What is wrong with it? Where else are you expecting it? >>>>=20 >>>> 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... ;-) >>>=20 >>> Ah, yeah, the new mailing list does not send you a copy of your own = email any more=E2=80=A6 >>>=20 >>> I don=E2=80=99t think we can change this on a per-user basis, but we = can globally. >>>=20 >>> Is this breaking anything for you or just unexpected? >>>=20 >> 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