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

Re: change remote to track new branch

From
Andreas Schwab <schwab@linux-m68k.org>
Date
Aug 3, 2013, 07:14 UTC
Message-ID
<m2d2pvp7nw.fsf@linux-m68k.org>
In-Reply-To
<20130803024032.GA28666@analysisandsolutions.com>
Daniel Convissor <danielc@analysisandsolutions.com> writes:
Show 9 quoted lines
> 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."
Previous: Daniel ConvissorNext: Daniel Convissor
Message 2 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.