From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.27 - Core Update 176 is available for testing
Date: Sat, 01 Jul 2023 10:05:18 +0100 [thread overview]
Message-ID: <14953D83-593B-4E8C-9251-9437368A24BA@ipfire.org> (raw)
In-Reply-To: <2b8530a5-7836-5075-6339-dbed09a64ba3@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
Thank you for your feedback.
I didn’t hear anything bad yet either.
-Michael
> On 29 Jun 2023, at 18:18, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
>
> Hi All,
>
> So far everything I have tested has worked as expected. That includes the OpenVPN roadwarrior connection.
>
> Looking good so far :crossed_fingers:
>
> Regards,
>
> Adolf.
>
>
> On 29/06/2023 12:20, IPFire Project wrote:
>> IPFire Logo
>> there is a new post from Peter Müller on the IPFire Blog:
>> *IPFire 2.27 - Core Update 176 is available for testing*
>> The next update, IPFire 2.27 - Core Update 176, is available for testing. It features a toolchain and package updates (among the security-relevant of them are Intel microcodes), brings the latest batch of bug fixes.
>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-176-is-available-for-testing>
>> The IPFire Project
>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
next prev parent reply other threads:[~2023-07-01 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <168803400577.813793.16129722323304756022.ipfire@ipfire.org>
2023-06-29 17:18 ` Adolf Belka
2023-07-01 9:05 ` Michael Tremer [this message]
2023-07-08 11:28 ` Peter Müller
2023-07-11 13:58 ` 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=14953D83-593B-4E8C-9251-9437368A24BA@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