Re: change remote to track new branch
- From
Daniel Convissor <danielc@analysisandsolutions.com>
- Date
- Aug 3, 2013, 16:28 UTC
- Message-ID
- <20130803162821.GA945@analysisandsolutions.com>
- In-Reply-To
- <m2d2pvp7nw.fsf@linux-m68k.org>
Hi Andreas:
On Sat, Aug 03, 2013 at 09:14:59AM +0200, Andreas Schwab wrote:
Show 15 quoted lines
> Daniel Convissor <danielc@analysisandsolutions.com> writes: > > > Long ago I added a remote to my repo. It is set to track what was then > > WordPress' main release branch (3.4-branch) and created a local branch > > to use it. Well, time marches on. I want to update my remote and > > branch to track the new main release branch (3.6-branch). > > > > Here's how I set things up at the time: > > > > git remote add -t 3.4-branch -f wp https://github.com/WordPress/WordPress > > git checkout -b wp wp/3.4-branch > > 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?
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
http://www.AnalysisAndSolutions.com/
4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335