Re: change remote to track new branch

Daniel Convissor [off-list ref] 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, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Hi Andreas:

On Sat, Aug 03, 2013 at 06:41:46PM +0200, Andreas Schwab wrote:

Daniel Convissor [off-list ref] 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.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)?

Thanks,

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

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.

Thank you,

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

On Tue, Aug 6, 2013 at 5:30 PM, Daniel Convissor
[off-list ref] wrote:

Hi Folks:

On Sat, Aug 03, 2013 at 12:52:15PM -0400, Daniel Convissor wrote:

quoted

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