public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Temporary branch for Core Update 164
Date: Sun, 16 Jan 2022 15:03:59 +0000	[thread overview]
Message-ID: <0A91FE79-3FD6-40DF-A2D7-25D1E38F1792@ipfire.org> (raw)
In-Reply-To: <6fbdce3e-1024-8149-2505-57af35dff41c@ipfire.org>

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

Hello,

> On 14 Jan 2022, at 21:24, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> Hello Arne,
> 
> for your convenience, I have set up a temporary branch for upcoming Core Update 164
> at https://git.ipfire.org/?p=people/pmueller/ipfire-2.x.git;a=shortlog;h=refs/heads/temp-c164-development .
> 
> Currently, it already includes:
> - Stefan's IDS multiple provider feature
> - The pakfire.cgi improvements done by Leo
> - A bunch of various updated packages
> - The firewall changes of mine
> 
> If you work on a kernel for Core Update 164, it would be great if you could take a look
> at the last 10 patches I made in https://git.ipfire.org/?p=people/pmueller/ipfire-2.x.git;a=shortlog;h=refs/heads/temp-kernel-changes .
> These are some security improvements I suggest to do, but the rootfiles for ARM are still
> missing. Also, I have no real ARM hardware to test these; just let me know what you think.

I can provide you with build stuff if you need to.

> 
> Thanks, and best regards,
> Peter Müller


      reply	other threads:[~2022-01-16 15:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 21:24 Peter Müller
2022-01-16 15:03 ` Michael Tremer [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=0A91FE79-3FD6-40DF-A2D7-25D1E38F1792@ipfire.org \
    --to=michael.tremer@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