From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: Where are all the pvops branches?
Date: Sun, 7 Mar 2010 09:33:11 +0000 [thread overview]
Message-ID: <4B9372D7.2030502@eu.citrix.com> (raw)
In-Reply-To: <1267902671.20243.70.camel@localhost.localdomain>
On 06/03/10 19:11, Ian Campbell wrote:
> On Sat, 2010-03-06 at 19:01 +0000, Keir Fraser wrote:
>> So I cloned git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git but
>> the result of 'git branch' is to list only xen/master, and if I try things
>> like 'git checkout xen/stable' then I get told there is no such branch. What
>> stupid thing am I doing wrong?
>
> You need "git branch -r" to show remote branches.
>
> xen/master needs to be prepended by the remote name, which defaults to
> origin unless you have been doing clever things with "git remote". Try
> "git checkout -b xen/stable origin/xen/stable" to checkout
> origin/xen/stable into a local branch called xen/stable.
if you want to track a remote branch, you probably want:
"git checkout --track origin/xen/stable"
which means you want to create a "xen/stable" local branch that track
the xen/stable branch on the "origin" remote (each time you pull
origin/xen/stable it will merge it automatically in your local
xen/stable branch).
Ian's command only creates a local "xen/stable" at the same reference
that origin/xen/stable is pointing too, but doesn't add the policy about
pull. you can easily add the tracking a-posteriori with:
"git branch --track xen/stable origin/xen/stable"
--
Vincent
next prev parent reply other threads:[~2010-03-07 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 19:01 Where are all the pvops branches? Keir Fraser
2010-03-06 19:11 ` Ian Campbell
2010-03-07 9:33 ` Vincent Hanquez [this message]
2010-03-06 21:10 ` Backport changeset 21002:7ed57b6e4cd to xen 3.4.3 Boris Derzhavets
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=4B9372D7.2030502@eu.citrix.com \
--to=vincent.hanquez@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).