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

Re: change remote to track new branch

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Aug 3, 2013, 17:05 UTC
Message-ID
<20130803170519.GC2893@elie.Belkin>
In-Reply-To
<20130803162821.GA945@analysisandsolutions.com>
Daniel Convissor wrote:
> On Sat, Aug 03, 2013 at 09:14:59AM +0200, Andreas Schwab wrote:
Show 6 quoted lines
>> Use "git remote set-branches" to change the tracked branches of a
>> remote.  Use "git branch --set-upstream-to" to change the upstream of a
>> branch (or create a new branch from the new upstream).
>
> Thanks.  Those commands were introduced in 1.8.  Is there a way to do it
> in 1.7, please?

"git remote set-branches" was introduced by v1.7.8-rc2~4^2~1. Are you stuck on 1.7.2.5, perhaps? In older (and current) versions of git, you can control the list of branches tracked by a remote by modifying its "fetch" refspec in .git/config:

	[remote "origin"]
		url = ...
		fetch = +refs/heads/master:refs/remotes/origin/master
		fetch = +refs/heads/next:refs/remotes/origin/next

"git branch --set-upstream-to" is from v1.8.0-rc0~50^2~4. In older versions of git,

	git branch --set-upstream-to=origin/master master
was spelled as
	git branch --set-upstream master origin/master

or the branch's upstream can be set directly in .git/config by modifying the "remote" and "merge" values in the [branch "foo"] paragraph.

Hope that helps, Jonathan

Previous: David Aguilar
Message 8 of 8 in “change remote to track new branch”
  1. Daniel ConvissorAug 3, 2013
  2. Andreas SchwabAug 3, 2013
  3. Daniel ConvissorAug 3, 2013
  4. Andreas SchwabAug 3, 2013
  5. Daniel ConvissorAug 3, 2013
  6. Daniel ConvissorAug 7, 2013
  7. David AguilarAug 7, 2013
  8. Jonathan NiederAug 3, 2013

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.