From: Bernhard Bitsch <bbitsch@ipfire.org>
To: IPFire Development <development@lists.ipfire.org>
Subject: Re: IPFire 2.29 - Core Update 203 is available for testing
Date: Wed, 10 Jun 2026 17:33:15 +0200 [thread overview]
Message-ID: <0ab751e0-e9a4-456d-bd63-93bbb87f0020@ipfire.org> (raw)
In-Reply-To: <178108477159.1728435.6056554574997819774.ipfire@ipfire.org>
Installation with no problems.
Great success in DNS resolving with RPZ. Runtime memory usage is smooth.
Congrats to the devs involved!
Regards
Bernhard
EDIT: My DNS status is broken.
next prev parent reply other threads:[~2026-06-10 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <178108477159.1728435.6056554574997819774.ipfire@ipfire.org>
2026-06-10 14:29 ` Bernhard Bitsch
2026-06-10 15:33 ` Bernhard Bitsch [this message]
2026-06-10 17:28 ` Bernhard Bitsch
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=0ab751e0-e9a4-456d-bd63-93bbb87f0020@ipfire.org \
--to=bbitsch@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