From: David Aguilar <davvid@gmail.com>
To: Daniel Convissor <danielc@analysisandsolutions.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: change remote to track new branch
Date: Tue, 6 Aug 2013 19:40:32 -0700 [thread overview]
Message-ID: <CAJDDKr5d=ifToosL2w5mJMyhiWwYK_eeuxEQTrDssVBe4P6JLA@mail.gmail.com> (raw)
In-Reply-To: <20130807003053.GA7145@analysisandsolutions.com>
On Tue, Aug 6, 2013 at 5:30 PM, Daniel Convissor
<danielc@analysisandsolutions.com> 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-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
next prev parent reply other threads:[~2013-08-07 2:40 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 [this message]
2013-08-03 17:05 ` Jonathan Nieder
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='CAJDDKr5d=ifToosL2w5mJMyhiWwYK_eeuxEQTrDssVBe4P6JLA@mail.gmail.com' \
--to=davvid@gmail.com \
--cc=danielc@analysisandsolutions.com \
--cc=git@vger.kernel.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).