git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Daniel Convissor <danielc@analysisandsolutions.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: change remote to track new branch
Date: Sat, 3 Aug 2013 10:05:19 -0700	[thread overview]
Message-ID: <20130803170519.GC2893@elie.Belkin> (raw)
In-Reply-To: <20130803162821.GA945@analysisandsolutions.com>

Daniel Convissor wrote:
> On Sat, Aug 03, 2013 at 09:14:59AM +0200, Andreas Schwab wrote:

>> 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

      parent reply	other threads:[~2013-08-03 17:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-03  2:40 change remote to track new branch Daniel Convissor
2013-08-03  7:14 ` Andreas Schwab
2013-08-03 16:28   ` Daniel Convissor
2013-08-03 16:41     ` Andreas Schwab
2013-08-03 16:52       ` Daniel Convissor
2013-08-07  0:30         ` Daniel Convissor
2013-08-07  2:40           ` David Aguilar
2013-08-03 17:05     ` Jonathan Nieder [this message]

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=20130803170519.GC2893@elie.Belkin \
    --to=jrnieder@gmail.com \
    --cc=danielc@analysisandsolutions.com \
    --cc=git@vger.kernel.org \
    --cc=schwab@linux-m68k.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.
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).