From: Jon Masters <jonathan@jonmasters.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Clark Williams <clark.williams@gmail.com>,
Gregory Haskins <ghaskins@novell.com>
Subject: Re: Creating the RT git tree
Date: Thu, 29 Jan 2009 16:06:40 -0500 [thread overview]
Message-ID: <1233263200.3937.44.camel@perihelion.bos.jonmasters.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0812161556460.25356@gandalf.stny.rr.com>
On Tue, 2008-12-16 at 17:36 -0500, Steven Rostedt wrote:
> This email is an explanation on how the RT git tree is created. Note, the
> tree is still in a "broken" state. But it now compiles!
Yay! I didn't spend enough time on this yet...but I'm poking at the
threadirqs branch at the moment. Some things I figured out:
*). The branches all seem to be remote. So you want to do something
like:
git checkout -b threadirqs origin/rt/threadirqs
(I guess on your box they're not referenced relative to origin :P)
*). I might not be the best git user on the planet (trying to fix that)
but I would really like to just see the patches that are specific to a
given topic branch, without the merge noise. For example, a git log on
the threadirqs branch shows me all the other patches in linus' tree as
merges are done. I could do a git log --grep="threadirqs" but is there a
better way? How do I instruct git to show me just the patches added
specifically in threadirqs?
Otherwise, looks cool. I've got a few machines I'd love to setup for
testing of the RT tree at home - if it's useful I have a 32-bit
Powerbook and a 64-bit IBM OpenPOWER (POWER5) that you might not
currently be doing build tests on?
I think I'll work on upstreamable threadirqs via my own branch of linus
rather than the RT tree - this should be pretty independent of RT for
now.
Jon.
next prev parent reply other threads:[~2009-01-29 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 22:36 Steven Rostedt
2009-01-29 21:06 ` Jon Masters [this message]
2009-01-29 22:07 ` john stultz
2009-01-29 22:15 ` Jon Masters
2009-01-29 22:54 ` Jon Masters
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=1233263200.3937.44.camel@perihelion.bos.jonmasters.org \
--to=jonathan@jonmasters.org \
--cc=acme@ghostprotocols.net \
--cc=clark.williams@gmail.com \
--cc=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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®