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

Re: [RFC/PATCH 1/2] remote tracking: return the tracking branch for the given branches

From
SBSanti Béjar <santi@agolina.net>
Date
Jun 18, 2009, 19:01 UTC
Message-ID
<adf1fd3d0906181201r5f3b2f55t8427e7be5ba07e9a@mail.gmail.com>
In-Reply-To
<adf1fd3d0906180740t637da9braea02deb3cba2680@mail.gmail.com>

One thing it just occurred to me is to return the explicit refspec instead of the tracking branch. So with the default config (after a clone):

$ git remote tracking origin refs/heads/master refs/heads/master:refs/remotes/origin/master

this makes a difference in case we want to allow returning all the matching tracking branch and not the first one with more than one branch, as:

$ git config remote.origin.fetch --add +refs/heads/*:refs/remote/another/*

$ git remote tracking origin refs/heads/master refs/heads/master:refs/remotes/origin/master refs/heads/next:refs/remotes/origin/next

$ git remote tracking origin refs/heads/master refs/heads/next refs/heads/master:refs/remotes/origin/master refs/heads/master:refs/remotes/another/master refs/heads/next:refs/remotes/origin/next refs/heads/next:refs/remotes/another/next

Thoughts?
Previous: Santi BéjarNext: Junio C Hamano
Message 11 of 19 in “Support for arbitrary mapping for "git pull --rebase"”
  1. 0/2 Support for arbitrary mapping for "git pull --rebase"Santi Béjar, Jun 18, 2009
  2. 1/2 remote tracking: return the tracking branch for the given branchesSanti Béjar, Jun 18, 2009
  3. Paolo BonziniJun 18, 2009
  4. Santi BéjarJun 18, 2009
  5. Johannes SchindelinJun 18, 2009
  6. Santi BéjarJun 18, 2009
  7. Jakub NarebskiJun 18, 2009
  8. Santi BéjarJun 18, 2009
  9. Jakub NarebskiJun 18, 2009
  10. Santi BéjarJun 18, 2009
  11. Santi BéjarJun 18, 2009
  12. Junio C HamanoJun 18, 2009
  13. Santi BéjarJun 18, 2009
  14. Santi BéjarJun 18, 2009
  15. 2/2 get_remote_merge_branch: Support for arbitrary mappingSanti Béjar, Jun 18, 2009
  16. Santi BéjarJun 18, 2009
  17. Johannes SchindelinJun 18, 2009
  18. Santi BéjarJun 18, 2009
  19. Santi BéjarJun 19, 2009

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.