From: Carsten Emde <C.Emde@osadl.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 3.10.6-rt3
Date: Tue, 13 Aug 2013 03:12:46 +0200 [thread overview]
Message-ID: <5209880E.6080902@osadl.org> (raw)
In-Reply-To: <CAP=VYLrd_ZU94Nf0X+FtT3M2Xx85t9FF13o-hV+_xHi7EjTf=w@mail.gmail.com>
On 08/13/2013 02:47 AM, Paul Gortmaker wrote:
> On Mon, Aug 12, 2013 at 3:48 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
>> On Mon, 12 Aug 2013 18:34:13 +0200
>> Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
>>
>>> Dear RT folks!
>>>
>>> I'm pleased to announce the v3.10.6-rt3 patch set.
>>
>> Does this mean that I can drop 3.6-rt in favor of 3.8-rt?
>
> I'd guess that the trade-off would be 3.0-rt against 3.8-rt.
> The above comment assumes 3.0 is aged out vs. 3.6 kernel.
>
>> I'm just about finished with a 3.6 stable, which I'll finish, add -rt
>> to it, and then call it "unsupported" after that. Well, I may take bug
>> fixes if people find any in the near future.
>>
>> I'm behind on 3.4-rt, 3.2-rt and of course 3.0-rt. Hopefully, I'll get
>> them all out this week.
>
> I expect that the 3.10-rt kernel will replace the older RT kernels.
We should not forget 3.2 that will be maintained until March 2016. Thus,
let's focus on 3.2 and 3.10 (maintained until August 2015) and abandon
all other 3.x RT versions.
-Carsten.
next prev parent reply other threads:[~2013-08-13 1:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 16:34 [ANNOUNCE] 3.10.6-rt3 Sebastian Andrzej Siewior
2013-08-12 19:48 ` Steven Rostedt
2013-08-13 0:47 ` Paul Gortmaker
2013-08-13 1:03 ` Steven Rostedt
2013-08-13 1:12 ` Carsten Emde [this message]
2013-08-13 10:54 ` Thomas Gleixner
2013-08-13 12:08 ` Steven Rostedt
[not found] ` <CAF+KLxsGtt_+0shjSGbjC4MG7i_yg1NL1zUXuVb-RiN=C44_nA@mail.gmail.com>
2013-08-14 18:17 ` Sebastian Andrzej Siewior
2013-08-14 18:21 ` Staffan Tjernstrom
2013-08-15 18:42 ` Fernando Lopez-Lezcano
2013-08-15 19:22 ` Steven Rostedt
2013-08-15 19:39 ` Fernando Lopez-Lezcano
2013-08-16 7:01 ` Sebastian Andrzej Siewior
2013-08-19 17:23 ` Fernando Lopez-Lezcano
2013-08-20 0:29 ` Steven Rostedt
2013-08-20 0:34 ` Fernando Lopez-Lezcano
2013-08-20 1:02 ` Steven Rostedt
2013-08-20 7:14 ` Sebastian Andrzej Siewior
2013-08-20 14:06 ` Steven Rostedt
2013-08-20 18:58 ` Fernando Lopez-Lezcano
[not found] ` <CAFfPn7iqf5EntPKdRO3cFhd=PFostp3mVLGEtt3ksLQHonMhkw@mail.gmail.com>
2013-08-27 16:19 ` Steven Rostedt
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=5209880E.6080902@osadl.org \
--to=c.emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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.