From: Tom Rymes <trymes@rymes.com>
To: development@lists.ipfire.org
Subject: Re: Core 121 - Updating machines using experimental kernels
Date: Wed, 13 Jun 2018 17:57:26 -0400 [thread overview]
Message-ID: <6C0D6C10-6D5D-42BA-B99A-AC4A400AED73@rymes.com> (raw)
In-Reply-To: <1d948e4fb1f77b71c55c458bc043cc3190e9cae0.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
Great news, thanks for the clarification, Michael.
Tom
> On Jun 13, 2018, at 5:49 PM, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>
> Hello,
>
> no, you can just install the update as soon as it is available in
> testing our released.
>
> The update will then remove the old (testing) kernel and install the
> new one.
>
> Best,
> -Michael
>
>> On Wed, 2018-06-13 at 12:38 -0400, Tom Rymes wrote:
>> I have a few machines here running Arne's experimental kernels for 4.14.
>> As I reported on the forum, they are still running well, but I wanted to
>> ask whether any special changes will need to be made before upgrading to
>> 121 when it is released, such as rolling back to the standard kernel.
>>
>> Many thanks,
>>
>> Tom
prev parent reply other threads:[~2018-06-13 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 16:38 Tom Rymes
2018-06-13 21:49 ` Michael Tremer
2018-06-13 21:57 ` Tom Rymes [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=6C0D6C10-6D5D-42BA-B99A-AC4A400AED73@rymes.com \
--to=trymes@rymes.com \
--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