git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: change remote to track new branch

From
Daniel Convissor <danielc@analysisandsolutions.com>
Date
Aug 3, 2013, 16:28 UTC
Message-ID
<20130803162821.GA945@analysisandsolutions.com>
In-Reply-To
<m2d2pvp7nw.fsf@linux-m68k.org>
Hi Andreas:
On Sat, Aug 03, 2013 at 09:14:59AM +0200, Andreas Schwab wrote:
Show 15 quoted lines
> 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
Previous: Andreas SchwabNext: Andreas Schwab
Message 3 of 8 in “change remote to track new branch”
  1. Daniel ConvissorAug 3, 2013
  2. Andreas SchwabAug 3, 2013
  3. Daniel ConvissorAug 3, 2013
  4. Andreas SchwabAug 3, 2013
  5. Daniel ConvissorAug 3, 2013
  6. Daniel ConvissorAug 7, 2013
  7. David AguilarAug 7, 2013
  8. Jonathan NiederAug 3, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.