From: Junio C Hamano <junkio@cox.net>
To: Bill Lear <rael@zopyra.com>
Cc: git@vger.kernel.org
Subject: Re: Pulling peer's branch and getting tracking branch created
Date: Mon, 26 Feb 2007 16:59:27 -0800 [thread overview]
Message-ID: <7v7iu4l8k0.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <17891.32095.655545.637691@lisa.zopyra.com> (Bill Lear's message of "Mon, 26 Feb 2007 18:37:51 -0600")
Bill Lear <rael@zopyra.com> writes:
> I can't seem to figure out the correct magic to get my buddy's branch,
> and create the appropriate tracking branch at the same time without
> doing a clone.
I'll cheat and ask "git show b6f5da1e" ;-).
$ git remote add -f -m master bob ../bob.git/
which should add:
[remote "bob"]
url = ../bob.git/
fetch = +refs/heads/*:refs/remotes/bob/*
to .git/config, and perform the initial "git fetch bob" so that
bob's heads appear under your .git/refs/remotes/bob/*, iow,
after this, you can ask:
$ git branch -r
bob/HEAD
bob/master
bob/topic-1
bob/topic-2
...
next prev parent reply other threads:[~2007-02-27 0:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 0:37 Pulling peer's branch and getting tracking branch created Bill Lear
2007-02-27 0:59 ` Junio C Hamano [this message]
2007-02-27 1:04 ` Bill Lear
2007-02-27 1:06 ` Junio C Hamano
2007-02-27 1:07 ` Bill Lear
2007-02-27 1:13 ` Junio C Hamano
2007-02-27 1:24 ` Bill Lear
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=7v7iu4l8k0.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=rael@zopyra.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