From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core Update 150 (Testing) feedback
Date: Mon, 05 Oct 2020 16:09:30 +0100 [thread overview]
Message-ID: <5200DE68-21EA-47FC-B902-B06C62710452@ipfire.org> (raw)
In-Reply-To: <ed92753e-ffe0-b534-b796-138a6a7da072@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
Hello,
Thank you very much for your feedback.
I have this running for a couple of weeks now, too. I will recommend an immediate release so that we can merge Core Update 151 into master and begin working on 152.
Best,
-Michael
> On 5 Oct 2020, at 14:50, Adolf Belka <ahb.ipfire(a)gmail.com> wrote:
>
> Hi everyone,
>
> Have been running Core Update 150 on my virtual test bed system for a few days now and no problems found with it.
>
>
> Regards,
>
> Adolf.
>
next prev parent reply other threads:[~2020-10-05 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 13:50 Adolf Belka
2020-10-05 15:09 ` Michael Tremer [this message]
2020-10-05 15:29 ` ummeegge
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=5200DE68-21EA-47FC-B902-B06C62710452@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