git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Qn about git pull and git fetch

From
Brian Gernhardt <brian@gernhardtsoftware.com>
Date
Sep 28, 2010, 20:01 UTC
Message-ID
<074C8233-BDFE-43AE-AF0A-2D510BF6F5DF@gernhardtsoftware.com>
In-Reply-To
<4CA2473B.2040600@nextest.com>
On Sep 28, 2010, at 3:51 PM, Eric Raible wrote:
Show 25 quoted lines
> 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?
Oops.  I had forgotten to change the first one after some experimenting on the git.git repo.  I had meant
$ git branch --set-upstream master origin/master
Far more repos have a master branch than a next one.
~~ Brian
Previous: Eric Raible
Message 5 of 5 in “Qn about git pull and git fetch”
  1. suvayu aliSep 28, 2010
  2. Brian GernhardtSep 28, 2010
  3. suvayu aliSep 28, 2010
  4. Eric RaibleSep 28, 2010
  5. Brian GernhardtSep 28, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.