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

Re: Tracking branches and pulling on remote

From
Jeff King <peff@peff.net>
Date
Jan 5, 2011, 16:44 UTC
Message-ID
<20110105164416.GA4393@sigill.intra.peff.net>
In-Reply-To
<4D249EFA.5050408@seznam.cz>
On Wed, Jan 05, 2011 at 05:40:26PM +0100, Maaartin-1 wrote:
Show 9 quoted lines
> >   $ git config remote.origin.fetch
> >   +refs/heads/*:refs/remotes/origin/*
> > 
> > which is a superset of what you added. If you run the git config command
> > I did above, what do you see?
> 
> No, there had been just the single line
> 
> refs/heads/master:refs/remotes/origin/master

Ah, OK, then that is the culprit. And the config line you added was a reasonable solution (though you may consider simply switching it to a wildcard to cover any future branches, too).

> OK, I swapped origin and upstream and made aliases
> 	fetchboth = !"git fetch; git fetch upstream"
> 	fetup = fetch upstream
> which is about everything I need for now.

Cool. You can also use "git fetch --all" to do the equivalent of your fetchboth.

-Peff
Previous: Maaartin-1
Message 4 of 4 in “Tracking branches and pulling on remote”
  1. MaaartinJan 5, 2011
  2. Jeff KingJan 5, 2011
  3. Maaartin-1Jan 5, 2011
  4. Jeff KingJan 5, 2011

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.