From: Paul Mundt <lethal@linux-sh.org>
To: Francis Moreau <francis.moro@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
matsu@igel.co.jp, linux-kernel@vger.kernel.org
Subject: Re: Why not creating a GIT RT tree ?
Date: Mon, 21 Jan 2008 16:45:24 +0900 [thread overview]
Message-ID: <20080121074524.GA20072@linux-sh.org> (raw)
In-Reply-To: <38b2ab8a0801191141g31137fe5m3b5fff35499588e5@mail.gmail.com>
On Sat, Jan 19, 2008 at 08:41:18PM +0100, Francis Moreau wrote:
> On Jan 18, 2008 8:12 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> > True, but then how would you do it. One thing is that most of these
> > branches would interact with each other. Touching the same code quite
> > a bit. So it doesn't always help. But pulling out patches can help us to
> > an extent.
> >
>
> I see, it would probably be too painful in this context, that's pity.
>
> >
> > Great! Looking forward to it ;-)
> >
>
> Well actually it seems already supported. Some files in arch/sh
> are already touched by RT patches.
>
At least it sees fairly regular testing on SH7751R and SH7780, you may
wish to discuss this with Matsubara-san (added to CC) though, as he does
most of the work in this area. I don't get much time to look at it.
next prev parent reply other threads:[~2008-01-21 7:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 13:44 Why not creating a GIT RT tree ? Francis Moreau
2008-01-18 15:55 ` Steven Rostedt
2008-01-18 17:37 ` Francis Moreau
2008-01-18 19:12 ` Steven Rostedt
2008-01-19 19:41 ` Francis Moreau
2008-01-21 7:45 ` Paul Mundt [this message]
2008-01-19 20:35 ` Jon Smirl
2008-01-18 21:59 ` James Cloos
2008-01-18 22:17 ` Steven Rostedt
2008-01-19 20:17 ` Francis Moreau
2008-01-19 22:39 ` James Cloos
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=20080121074524.GA20072@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=francis.moro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matsu@igel.co.jp \
--cc=rostedt@goodmis.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.