From: Jon Masters <jonathan@jonmasters.org>
To: john stultz <johnstul@us.ibm.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
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 17:54:12 -0500 [thread overview]
Message-ID: <1233269652.3937.74.camel@perihelion.bos.jonmasters.org> (raw)
In-Reply-To: <1233267328.3937.66.camel@perihelion.bos.jonmasters.org>
On Thu, 2009-01-29 at 17:15 -0500, Jon Masters wrote:
> On Thu, 2009-01-29 at 14:07 -0800, john stultz wrote:
>
> > git log -r origin/linus..origin/rt/threadirqs
>
> Ok. So perhaps it's the branch creation during:
>
> git checkout -b threadirqs origin/rt/threadirqs
>
> Because yeah, that does show what I want. This is weird. Is there some
> git expert who can tell me why I'm seeing linus merges in my local
> branch? My local branch should be simply the same as the remote one...
Bah. I think I was just fat-fingering something. Ok, so it does actually
work if I do this:
git log master...threadirqs
or replace master with $whatever. Ok, that's really what I wanted. It
would be nice if a branch could be setup without all the merge history
builtin - that's supposed to be in the rt-master and so forth
branches...but whatever.
Jon.
prev parent reply other threads:[~2009-01-29 22:54 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
2009-01-29 22:07 ` john stultz
2009-01-29 22:15 ` Jon Masters
2009-01-29 22:54 ` Jon Masters [this message]
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=1233269652.3937.74.camel@perihelion.bos.jonmasters.org \
--to=jonathan@jonmasters.org \
--cc=acme@ghostprotocols.net \
--cc=clark.williams@gmail.com \
--cc=ghaskins@novell.com \
--cc=johnstul@us.ibm.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®