git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Daniel Convissor <danielc@analysisandsolutions.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: change remote to track new branch
Date: Sat, 3 Aug 2013 12:28:21 -0400	[thread overview]
Message-ID: <20130803162821.GA945@analysisandsolutions.com> (raw)
In-Reply-To: <m2d2pvp7nw.fsf@linux-m68k.org>

Hi Andreas:

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

Thanks.  Those commands were introduced in 1.8.  Is there a way to do it
in 1.7, please?

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

  reply	other threads:[~2013-08-03 16:28 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 [this message]
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

  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=20130803162821.GA945@analysisandsolutions.com \
    --to=danielc@analysisandsolutions.com \
    --cc=git@vger.kernel.org \
    --cc=schwab@linux-m68k.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).