From: Steven Rostedt <rostedt@goodmis.org>
To: Rick Wright <riwright@vt.edu>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [Announce] RT patch updates while Ingo is busy
Date: Fri, 06 Jan 2006 12:54:28 -0500 [thread overview]
Message-ID: <1136570068.12468.149.camel@localhost.localdomain> (raw)
In-Reply-To: <43BEA35D.5030301@vt.edu>
On Fri, 2006-01-06 at 12:05 -0500, Rick Wright wrote:
> Steve,
>
> I noticed that 2.6.15-rc2 was released in Ingo's usual place yesterday
> (1/5/06) which seems to post-date your 2.6.15-rcX-srX branch. Then,
> earlier today you hinted at an impending 2.6.15-rc1-sr2 release.
> Could you explain how your patches are related to Ingo's -rc2 patch as
> they seem to be somewhat interleaved?
My patches are for going between Ingo's releases. I've even released
2.6.15-rt1-sr2, for the simple reason I didn't notice that 2.6.15-rt2
was out :)
So I'll now download 2.6.15-rt2 and see where it's at. So my suggestion
is to always pick the latest -rt kernel, and if it doesn't work, try my
-sr patch for the same release.
>
> Also, I didn't include the other's on this mail or cc LKML as I'm not
> sure if this was appropriate. If you believe others should be
> included, please include them and forgive my exclusion.
I've added both Ingo and the lkml just so others know. As the title
says, the -sr branch is only while Ingo is busy doing other things, but
I'll keep my branches posted anyways.
-- Steve
prev parent reply other threads:[~2006-01-06 17:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 17:32 RT : 2.6.15-rt1 and net/ipv6/mcast.c Serge Noiraud
2006-01-04 20:34 ` Daniel Walker
2006-01-04 22:12 ` Steven Rostedt
2006-01-05 2:11 ` [Announce] RT patch updates while Ingo is busy Steven Rostedt
[not found] ` <43BEA35D.5030301@vt.edu>
2006-01-06 17:54 ` Steven Rostedt [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=1136570068.12468.149.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=riwright@vt.edu \
/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
all inboxes | Powered by JetHome®