Re: change remote to track new branch

From: David Aguilar <davvid@gmail.com>
Date: Aug 7, 2013, 02:40 UTC
Message-ID: <CAJDDKr5d=ifToosL2w5mJMyhiWwYK_eeuxEQTrDssVBe4P6JLA@mail.gmail.com>
In-Reply-To: <20130807003053.GA7145@analysisandsolutions.com>

On Tue, Aug 6, 2013 at 5:30 PM, Daniel Convissor <danielc@analysisandsolutions.com> wrote:

Show 16 quoted lines

> 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"
>>
>> So is "git remote set-branches" and "git branch --set-upstream-to" just
>> another syntax for making those same changes to git config?  Or do the
>> new commands do some additional work on the repository (to better keep
>> track of things, or whatever)?
>
> Sorry to be a pest, but I'm curious what the answer is, please.

There's really nothing more to it.

There is one other setting -- "branch.wp.remote" should be set to "wp".

If you edit your .git/config by hand you'll see what's really going on. It's quite simple under the hood.

-- 
David