From: Clark Williams <williams@redhat.com>
To: Robert Barrows <Robert.Barrows@metriainnovation.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Determining latest stable release.
Date: Wed, 28 Mar 2012 14:00:22 -0500 [thread overview]
Message-ID: <20120328140022.2998bfbc@redhat.com> (raw)
In-Reply-To: <CAOHJ0jQphT30v-y1HMiHYOnFVumovkccCV43mDJjBx=fko=GUg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
On Tue, 27 Mar 2012 15:59:31 -0500
Robert Barrows <Robert.Barrows@metriainnovation.com> wrote:
> Does the PREEMPT_RT patch have a method of determining latest stable
> release?
>
> I notice that 3.0.35 goes up to rt44 was declared a stable release but
> so was rt43
> Now 3.2.12 goes up to rt22, and that was updated March 23rd with 3.0.35-rt44.
>
> Is there a reason to think that 3.0.35-rt44 is more stable than 3.2.12-rt22?
> The real question is: is there a rule of thumb on how you would choose
> a rt patched kernel for a production machine?
>
> Thanks.
>
> -Robb Barrows
> --
>
The stuff that Steven releases is the stable series, while Thomas
does the devel releases. So if you're not looking for the latest and
greatest, I'd stick to what Steven releases.
Clark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-03-28 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOHJ0jTVxzgfBK=GSEr14YrpFZEqFE_qDqftaUgGWDgm344NNg@mail.gmail.com>
2012-03-27 20:59 ` Determining latest stable release Robert Barrows
2012-03-28 19:00 ` Clark Williams [this message]
2012-03-28 20:27 ` Wolfgang Wallner
2012-03-28 20:34 ` Clark Williams
2012-03-28 22:08 ` Carsten Emde
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=20120328140022.2998bfbc@redhat.com \
--to=williams@redhat.com \
--cc=Robert.Barrows@metriainnovation.com \
--cc=linux-rt-users@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.