From: Andreas Schwab <schwab@linux-m68k.org>
To: Daniel Convissor <danielc@analysisandsolutions.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: change remote to track new branch
Date: Sat, 03 Aug 2013 09:14:59 +0200 [thread overview]
Message-ID: <m2d2pvp7nw.fsf@linux-m68k.org> (raw)
In-Reply-To: <20130803024032.GA28666@analysisandsolutions.com> (Daniel Convissor's message of "Fri, 2 Aug 2013 22:40:32 -0400")
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).
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."
next prev parent reply other threads:[~2013-08-03 7:15 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2d2pvp7nw.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.