public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: jon <jon.murphy@ipfire.org>
To: development@lists.ipfire.org
Subject: Fwd: IPFire 2.27 - Core Update 177 is available for testing
Date: Thu, 27 Jul 2023 13:46:25 -0500	[thread overview]
Message-ID: <FB3E041E-ECF4-49C4-BD34-5490D42081D2@ipfire.org> (raw)
In-Reply-To: <169046280863.981793.753654633675135433.ipfire@ipfire.org>

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

Peter / Michael,

Did this patch get placed into CU 177?

https://patchwork.ipfire.org/project/ipfire/patch/20230713170349.3479430-1-adolf.belka(a)ipfire.org/


It is the sister fix for the pmacct issues:

https://patchwork.ipfire.org/project/ipfire/patch/20230706210506.983914-1-jon.murphy(a)ipfire.org/



Jon Murphy
jon.murphy(a)ipfire.org



> Begin forwarded message:
> 
> From: IPFire Project <no-reply(a)ipfire.org>
> Subject: IPFire 2.27 - Core Update 177 is available for testing
> Date: July 27, 2023 at 8:00:08 AM CDT
> To: Jon <jon.murphy(a)ipfire.org>
> 
> 
> there is a new post from Michael Tremer on the IPFire Blog:
> 
> IPFire 2.27 - Core Update 177 is available for testing
> 
> The next update for IPFire is available for testing! It contains more hardening features for modern processors and a large number of security fixes in third-party packages.
> CLICK HERE TO READ MORE
> The IPFire Project 
> Don't like these emails? Unsubscribe.


           reply	other threads:[~2023-07-27 18:46 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <169046280863.981793.753654633675135433.ipfire@ipfire.org>]

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=FB3E041E-ECF4-49C4-BD34-5490D42081D2@ipfire.org \
    --to=jon.murphy@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