From: Tomas Carnecky <tomas.carnecky@gmail.com>
To: Woody Wu <narkewoody@gmail.com>, git@vger.kernel.org
Subject: Re: How to specify remote branch correctly
Date: Mon, 17 Dec 2012 07:21:44 +0000 [thread overview]
Message-ID: <1355728904-ner-4851@calvin> (raw)
In-Reply-To: <slrnkctgqh.mmj.narkewoody@zuhnb712.local.com>
On Mon, 17 Dec 2012 07:02:46 +0000, Woody Wu <narkewoody@gmail.com> wrote:
> On 2012-12-17, Tomas Carnecky <tomas.carnecky@gmail.com> wrote:
> > 'git checkout foo' has special meaning if a local branch with that
> > name doesn't exist but there is a remote branch with that name. In
> > that case it's equivalent to: git checkout -t -b foo origin/foo.
> > Because that's what people usually want.
>
> I think this is what exactly happened to me in the first time I got the
> 'foo'. One new thing to me is the '-t'. I am not sure wether the '-t'
> was used or not in the background. How do I check the 'upstream'
> relationships? Is there any file under .git recoreded that kind of
> information?
Yes, that information is recorded in a file somewhere in .git. However, for
most users it's irrelevant which file it is. Git has commands to access this
information. Try one of these:
git branch -vv
git remote show origin
git rev-parse --abbrev-ref --symbolic-full-name @{u}
next prev parent reply other threads:[~2012-12-17 7:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 2:30 How to specify remote branch correctly Woody Wu
2012-12-17 4:27 ` Andrew Ardill
2012-12-17 5:06 ` Woody Wu
2012-12-17 5:13 ` Andrew Ardill
2012-12-17 5:30 ` Tomas Carnecky
2012-12-17 5:52 ` Andrew Ardill
2012-12-17 6:44 ` Chris Rorvick
2012-12-17 7:02 ` Woody Wu
2012-12-17 7:21 ` Tomas Carnecky [this message]
2012-12-17 7:41 ` Woody Wu
2012-12-17 6:48 ` Woody Wu
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1355728904-ner-4851@calvin \
--to=tomas.carnecky@gmail.com \
--cc=git@vger.kernel.org \
--cc=narkewoody@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).