From: "Francis Moreau" <francis.moro@gmail.com>
To: "Steven Rostedt" <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why not creating a GIT RT tree ?
Date: Fri, 18 Jan 2008 18:37:24 +0100 [thread overview]
Message-ID: <38b2ab8a0801180937y4264fc15wd3b91ca74635f679@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0801180947180.7574@gandalf.stny.rr.com>
Hello,
On Jan 18, 2008 4:55 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Fri, 18 Jan 2008, Francis Moreau wrote:
>
> > Maybe I missed it but I'm wondering why GIT is not used for
> > the RT development ? I can't find a rt tree anywhere and all
> > new rt release spoke about a patchset to apply on mainline
> > kernels.
>
> The answer to this is pretty much the same as why the -mm tree isn't in
> git either.
>
Well not exactly. Unlike the mm tree which is made of a lots of patches
dealing with totaly unrelated subjects, the rt patches only hopefully deal
with realtime stuffs.
> The RT tree is made up of lots of patches (over 300). Our goal is to get
> RT into mainline Linux. RT isn't just one type of system, it extends all
> over the kernel, and the patches may be rewriten over and over. Managing
> this in quilt is a lot easier than managing it in git.
>
I'm probably missing something since I haven't looked at the RT patches
(yet) but couldn't these 300 patches be sorted out by topics ?
If so you could create a branch per topic and merge all of them in your
master branch which would be the rt kernel. Hopefully each branch
won't interact with other branch too much.
All of this assumes of course that the number of topics is definitely much
smaller than the number of patches (~300).
Having such a tree would be very useful for looking at history in each topic,
for doing some git-bisect debug session IMHO...
> That said, there's been talk about making a git tree for others based on
> the quilt queue. The thing is that a new git tree will need to be created
> for every release. Which means that it will be difficult for others to
> simply update their local repo since you will get a bunch of errors with
> not being from the same head.
>
>
> >
> > Another question, is there a TODO list somewhere which would
> > help to port the RT patch to a new architecture ?
>
> Which arch? We are already on PowerPC, ARM and MIPS. Thinking about sh?
>
Yep, not that I'm an expert in this architecture but it's commonly used
in multimedia device where realtime is often needed.
Thanks
--
Francis
next prev parent reply other threads:[~2008-01-18 17:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 13:44 Francis Moreau
2008-01-18 15:55 ` Steven Rostedt
2008-01-18 17:37 ` Francis Moreau [this message]
2008-01-18 19:12 ` Steven Rostedt
2008-01-19 19:41 ` Francis Moreau
2008-01-21 7:45 ` Paul Mundt
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=38b2ab8a0801180937y4264fc15wd3b91ca74635f679@mail.gmail.com \
--to=francis.moro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome