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

Re: confusion over the new branch and merge config

From
Jeff King <peff@peff.net>
Date
Dec 23, 2006, 06:28 UTC
Message-ID
<20061223062801.GA5415@segfault.peff.net>
In-Reply-To
<7vbqlvuoi4.fsf@assigned-by-dhcp.cox.net>
On Fri, Dec 22, 2006 at 10:15:15PM -0800, Junio C Hamano wrote:
Show 5 quoted lines
> Only *if* you store it in that tracking branch.  The name the
> other party gives _do_ matter to you anyway, because you have to
> _know_ it to fetch.  What it does NOT matter is if you use a
> tracking branch, or if you do, which local tracking branch you
> use to track it.

No, their names _don't_ matter to most users. With the new remote layout and wildcards, I'll never even see 'refs/heads/next' when I clone git.git; I'll only talk about 'origin/next'. The local tracking branch matters much more to me, because it's the thing I'll use to interact with git. I don't say 'git-checkout -b topic origin refs/heads/master'; I say 'git-checkout -b topic origin/next'.

Yes, my proposed syntax means you have to have a tracking branch. But does it really make sense for people to put entries in their config file, but not have a tracking branch? What do people use non-tracking branch pulls for, anyway? I would assume for one-off pulls of infrequently used repositories, in which case they're always saying "git-pull git://path/to/repo foo:bar". My point being that if we can improve the usefulness of the config file, it's probably not worth worrying about people combining branch.*.merge config entries with non-tracking-branch pulls, since they're extremely unlikely to be used together.

Does anyone out there use non-tracking-branch pulls? If so, can you describe your use case?

-Peff
Previous: Shawn PearceNext: Junio C Hamano
Message 23 of 45 in “confusion over the new branch and merge config”
  1. Nicolas PitreDec 21, 2006
  2. Junio C HamanoDec 21, 2006
  3. SeanDec 21, 2006
  4. Junio C HamanoDec 22, 2006
  5. Junio C HamanoDec 22, 2006
  6. SeanDec 22, 2006
  7. Andy ParkinsDec 22, 2006
  8. Alan ChandlerDec 22, 2006
  9. Junio C HamanoDec 22, 2006
  10. Andy ParkinsDec 22, 2006
  11. Alan ChandlerDec 22, 2006
  12. Nicolas PitreDec 22, 2006
  13. Jakub NarebskiDec 22, 2006
  14. Nicolas PitreDec 22, 2006
  15. Jakub NarebskiDec 22, 2006
  16. Junio C HamanoDec 22, 2006
  17. Tom PrinceDec 23, 2006
  18. Nicolas PitreDec 23, 2006
  19. Jeff KingDec 23, 2006
  20. Nicolas PitreDec 23, 2006
  21. Junio C HamanoDec 23, 2006
  22. Shawn PearceDec 23, 2006
  23. Jeff KingDec 23, 2006
  24. Junio C HamanoDec 23, 2006
  25. Jeff KingDec 23, 2006
  26. Junio C HamanoDec 23, 2006
  27. Jakub NarebskiDec 23, 2006
  28. Johannes SchindelinDec 23, 2006
  29. Jakub NarebskiDec 23, 2006
  30. Jeff KingDec 24, 2006
  31. Nicolas PitreDec 24, 2006
  32. Jeff KingDec 26, 2006
  33. Jeff KingJan 2, 2007
  34. Junio C HamanoJan 2, 2007
  35. Jeff KingJan 2, 2007
  36. Junio C HamanoJan 2, 2007
  37. Jakub NarebskiJan 2, 2007
  38. Santi BéjarJan 3, 2007
  39. Jakub NarebskiJan 3, 2007
  40. Jeff KingJan 9, 2007
  41. Jeff KingJan 9, 2007
  42. Jakub NarebskiDec 23, 2006
  43. Andy ParkinsDec 22, 2006
  44. Lars HjemliDec 22, 2006
  45. Nicolas PitreDec 22, 2006

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.