From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Couple of patches not merged yet
Date: Sat, 06 Jan 2024 14:21:00 +0000 [thread overview]
Message-ID: <f0cf4f49-8afa-4338-b9ab-50e25532f697@ipfire.org> (raw)
In-Reply-To: <DD48E500-FB74-4E9C-8342-5191C7D45CC2@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
Hello Adolf, hello Michael,
I was just about to reply... :-)
> Hello Adolf,
>
> Peter volunteered to merge all patches.
Yes. :-)
>
> From my point of view they look fine. I suppose he just forgot about them?!
Not really, I meant to have a closer look at both the other day, but due
to some ${dayjob} snafu I haven't had time to review the remaining ones
before merging them.
This is on my docket list for today. Apologies for the delay.
Thanks, and best regards,
Peter Müller
>
> -Michael
>
>> On 5 Jan 2024, at 14:24, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi Peter and Michael,
>>
>> Most of the patches I have submitted for IPFire-2.x have been merged.
>>
>> There are just two outstanding. I was wondering if these have been overlooked or if there is a problem with them.
>>
>> The patches are for bash and postfix.
>>
>> https://patchwork.ipfire.org/project/ipfire/patch/20231218172911.2531726-1-adolf.belka(a)ipfire.org/
>> https://patchwork.ipfire.org/project/ipfire/patch/20231226131036.3260423-3-adolf.belka(a)ipfire.org/
>>
>> I am especially interested in the second one related to postfix and stopping the smtp smuggling vulnerability on the postfix addon.
>>
>> Let me know if I need to modify anything.
>>
>> Regards,
>>
>> Adolf.
>>
>> --
>> Sent from my laptop
>>
>
prev parent reply other threads:[~2024-01-06 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 14:24 Adolf Belka
2024-01-06 14:11 ` Michael Tremer
2024-01-06 14:21 ` Peter Müller [this message]
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=f0cf4f49-8afa-4338-b9ab-50e25532f697@ipfire.org \
--to=peter.mueller@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