From: Eric Raible <raible@nextest.com>
To: Brian Gernhardt <brian@gernhardtsoftware.com>
Cc: suvayu ali <fatkasuvayu+linux@gmail.com>, <git@vger.kernel.org>
Subject: Re: Re: Qn about git pull and git fetch
Date: Tue, 28 Sep 2010 12:51:23 -0700 [thread overview]
Message-ID: <4CA2473B.2040600@nextest.com> (raw)
In-Reply-To: <9732E43E-124D-4145-A289-2E78F2277ACE@gernhardtsoftware.com>
On 11:59 AM, Brian Gernhardt wrote:
>
> Your branches should be set to track automatically but if they didn't for
> some reason and are using v1.7.0 or newer, you can:
>
> $ git branch --set-upstream master origin/next
> Branch master set up to track remote branch next from origin.
> $ git pull
>
> If you're using git prior to v1.7.0, you can instead:
>
> $ git config branch.master.remote origin
> $ git config branch.master.merge refs/heads/master
> $ git pull
Seems to me that to be equivalent, the first should be:
git branch --set-upstream master origin/master
or the second should be:
git config branch.master.merge refs/heads/next
Eh?
next prev parent reply other threads:[~2010-09-28 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 16:59 Qn about git pull and git fetch suvayu ali
2010-09-28 17:33 ` Brian Gernhardt
2010-09-28 19:09 ` suvayu ali
2010-09-28 19:51 ` Eric Raible [this message]
2010-09-28 20:01 ` Brian Gernhardt
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=4CA2473B.2040600@nextest.com \
--to=raible@nextest.com \
--cc=brian@gernhardtsoftware.com \
--cc=fatkasuvayu+linux@gmail.com \
--cc=git@vger.kernel.org \
/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).