From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Steven Rostedt" <rostedt@goodmis.org>
Cc: "Francis Moreau" <francis.moro@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Why not creating a GIT RT tree ?
Date: Sat, 19 Jan 2008 15:35:12 -0500 [thread overview]
Message-ID: <9e4733910801191235k5ccd247cka2f6bf2a10dbd3a4@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0801180947180.7574@gandalf.stny.rr.com>
On 1/18/08, 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.
>
> 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.
>
> 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.
stgit is worth checking out. It's basically quilt for git. I'm using
to juggle about 30 patches.
I believe there is a way to set up the git config file on the server
to force updating clients onto the new head without triggering an
error messages.
Ask on the git list and you'll get at least a dozen different
suggestions on how to make your repo available on git.
>
>
> >
> > 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?
>
> The best would be to read the code and look at my paper:
>
> http://ols.108.redhat.com/2007/Reprints/rostedt-Reprint.pdf
> (Internals of the RT Patch)
>
> This will give you an idea of what is needed to port to another arch.
>
> >
> > Sorry if the questions are dumbed but I'm just new to this
> > project.
>
> No, in fact, I think it's about time to add these to our FAQ:
>
> http://rt.wiki.kernel.org/index.php/Frequently_Asked_Questions
>
> Thanks,
>
> -- Steve
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2008-01-19 20:35 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
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 [this message]
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=9e4733910801191235k5ccd247cka2f6bf2a10dbd3a4@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=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
all inboxes | Powered by JetHome®