Re: change remote to track new branch

2013-08-06 Thread David Aguilar
On Tue, Aug 6, 2013 at 5:30 PM, Daniel Convissor wrote: > Hi Folks: > > On Sat, Aug 03, 2013 at 12:52:15PM -0400, Daniel Convissor wrote: >> >> Yeah. I had contemplated using the following commands: >> >> git config remote.wp.fetch \ >> "+refs/heads/3.6-branch:refs/remotes/wp/3.6-bran

Re: change remote to track new branch

2013-08-06 Thread Daniel Convissor
Hi Folks: On Sat, Aug 03, 2013 at 12:52:15PM -0400, Daniel Convissor wrote: > > Yeah. I had contemplated using the following commands: > > git config remote.wp.fetch \ > "+refs/heads/3.6-branch:refs/remotes/wp/3.6-branch" > git config branch.wp.merge "refs/heads/3.6-branch" > >

Re: change remote to track new branch

2013-08-03 Thread Jonathan Nieder
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). > > Th

Re: change remote to track new branch

2013-08-03 Thread Daniel Convissor
Hi Andreas: On Sat, Aug 03, 2013 at 06:41:46PM +0200, Andreas Schwab wrote: > Daniel Convissor writes: > > Use git config. Yeah. I had contemplated using the following commands: git config remote.wp.fetch \ "+refs/heads/3.6-branch:refs/remotes/wp/3.6-branch" git config branch.

Re: change remote to track new branch

2013-08-03 Thread Andreas Schwab
Daniel Convissor writes: > Thanks. Those commands were introduced in 1.8. Is there a way to do it > in 1.7, please? Use git config. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely di

Re: change remote to track new branch

2013-08-03 Thread Daniel Convissor
Hi Andreas: On Sat, Aug 03, 2013 at 09:14:59AM +0200, Andreas Schwab wrote: > Daniel Convissor 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.

Re: change remote to track new branch

2013-08-03 Thread Andreas Schwab
Daniel Convissor 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-branc

change remote to track new branch

2013-08-02 Thread Daniel Convissor
Hi: 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 u