git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mikael Magnusson" <mikachu@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: mingo@elte.hu, git@vger.kernel.org
Subject: Re: linux-x86-tip: pilot error?
Date: Sun, 22 Jun 2008 14:48:35 +0200	[thread overview]
Message-ID: <237967ef0806220548t3fd73211v354071efe2db22e4@mail.gmail.com> (raw)
In-Reply-To: <20080622123620.GA9328@linux.vnet.ibm.com>

2008/6/22 Paul E. McKenney <paulmck@linux.vnet.ibm.com>:
> Hello, Ingo,
>
> I took the precaution of rebuilding my linux-2.6-tip from scratch as follows:
>
>  544  mkdir linux-2.6-tip
>  545  cd linux-2.6-tip
>  546  git-init-db
>  547  git-remote add linus git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>  548  git-remote add tip git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
>  549  git-remote update
>  550  git-checkout tip-core-rcu-2008-06-16_09.23_Mon

When checking out remote branches, you have to specify the remote:
git checkout tip/tip-blabla
(it'll warn about detaching HEAD, this is normal).

-- 
Mikael Magnusson

  reply	other threads:[~2008-06-22 12:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-22 12:36 linux-x86-tip: pilot error? Paul E. McKenney
2008-06-22 12:48 ` Mikael Magnusson [this message]
2008-06-22 13:21   ` Paul E. McKenney
2008-06-22 21:11     ` Mikael Magnusson
2008-06-22 21:42     ` Björn Steinbrink
2008-06-22 22:21       ` Paul E. McKenney
2008-06-23  7:14     ` Ingo Molnar
2008-06-23  9:57       ` Paul E. McKenney
2008-06-23 10:24         ` Ingo Molnar
2008-06-23 11:11           ` Paul E. McKenney
2008-06-23 11:22             ` Ingo Molnar
2008-06-23 16:14               ` Daniel Barkalow
2008-06-23 15:12       ` Jeff King
2008-06-23 15:31         ` Ingo Molnar
2008-06-23 16:05         ` Ingo Molnar

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=237967ef0806220548t3fd73211v354071efe2db22e4@mail.gmail.com \
    --to=mikachu@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulmck@linux.vnet.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).