From: James Cloos <cloos@jhcloos.com>
To: "Francis Moreau" <francis.moro@gmail.com>
Cc: rostedt@goodmis.org, linux-kernel@vger.kernel.org
Subject: Re: Why not creating a GIT RT tree ?
Date: Fri, 18 Jan 2008 21:59:22 +0000 [thread overview]
Message-ID: <m3zlv2kd6t.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <38b2ab8a0801180544j2022af8bl252a118a295b1f34@mail.gmail.com> (Francis Moreau's message of "Fri, 18 Jan 2008 14:44:38 +0100")
>>>>> "Francis" == Francis Moreau <francis.moro@gmail.com> writes:
Francis> I can't find a rt tree anywhere and all new rt release spoke
Francis> about a patchset to apply on mainline kernels.
It is not perfect, but I do have a git repo of the rt history-of-patches
up at:
git://git.kernel.org/pub/scm/linux/kernel/git/cloos/rt-2.6.git
http://www.kernel.org/pub/scm/linux/kernel/git/cloos/rt-2.6.git
Gitweb URL is:
http://git.kernel.org/?p=linux/kernel/git/cloos/rt-2.6.git
It is in the one-head per patch style, and has the single-file patches
applied rather than the quilt queue.
But it will at least allow comparisons among the various versions.
The master head matches the most current patch.
(I try to keep it updated the same day as patches are announced, but
it does sometimes lag a day or two.)
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2008-01-18 22:07 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
2008-01-18 21:59 ` James Cloos [this message]
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=m3zlv2kd6t.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.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
Powered by JetHome