public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Planning Core Update 155
Date: Fri, 12 Mar 2021 15:23:15 +0100	[thread overview]
Message-ID: <48785cc8-0a08-3f81-f83a-3ea677b8ed94@ipfire.org> (raw)
In-Reply-To: <7E94147D-81F7-434A-852A-256DB2700D53@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]

Hi all,

On 10/03/2021 14:38, Michael Tremer wrote:
> Hello everyone,
>
> I wanted to open a quick thread to organise what is going into the next Core Update which I planned on closing soon so that people have more time to test the ALG changes that have been announced yesterday:
>
>    https://blog.ipfire.org/post/security-announcement-mitigating-nat-slipstreaming
>
> It was being quiet and so I wanted to wait until armv5tel finally builds again and then branch the update. Now there is a massive wave of packages from Adolf which should probably be included in this release. Just to keep the backlog as small as possible.
>
> Does anybody else have any pending changes that should go into c155?
I don't currently have any additional ones. I found most of the previous 
ones because they were updated in my Arch Linux systems so that flagged 
me to check them in IPFire.

If I find any new ones I will hold them till Core 155 has been issued 
for testing.

Regards,

Adolf.

> Best,
> -Michael

-- 
Sent from my laptop


  reply	other threads:[~2021-03-12 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 13:38 Michael Tremer
2021-03-12 14:23 ` Adolf Belka [this message]
2021-03-14 13:03   ` Adolf Belka
2021-03-15 13:48     ` 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=48785cc8-0a08-3f81-f83a-3ea677b8ed94@ipfire.org \
    --to=adolf.belka@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