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

Re: (unknown)

From
JWJosef Weidendorfer <josef.weidendorfer@gmx.de>
Date
Oct 26, 2006, 13:22 UTC
Message-ID
<200610261522.44433.Josef.Weidendorfer@gmx.de>
In-Reply-To
<7vwt6okpgr.fsf@assigned-by-dhcp.cox.net>
On Thursday 26 October 2006 00:20, Junio C Hamano wrote:
Show 5 quoted lines
> Heh, I spoke too fast.
> 
> 	"git log origin..master"
> 
> If you do not have none of .git/origin
Really? I thought refs are always looked up in ".git/refs" only?
> , .git/refs/origin, 
> .git/refs/tags/origin, .git/refs/heads/origin, nor
> .git/refs/remotes/origin, then .git/refs/remotes/origin/HEAD is
> what "origin" means (see get_sha1_basic() in sha1_name.c).
Yes.

However, IMHO it really should be a alias to "remotes/origin/<branch>", depending on current "<branch>" you are on. AFAI can remember, when implementing it, HEAD was choosen as sha1_name.c should not cope with porcelain issues (e.g. getting current branch name). It was the intention to change remotes/origin/HEAD in the porcelain command before actual use.

Is this still sensible?
Previous: Jakub NarebskiNext: Linus Torvalds
Message 12 of 14 in “(unknown)”
  1. andyparkins@gmail.comOct 25, 2006
  2. Jakub NarebskiOct 25, 2006
  3. Andy ParkinsOct 25, 2006
  4. Karl HasselströmOct 25, 2006
  5. Junio C HamanoOct 25, 2006
  6. Andy ParkinsOct 25, 2006
  7. Junio C HamanoOct 25, 2006
  8. Junio C HamanoOct 25, 2006
  9. Andy ParkinsOct 26, 2006
  10. Documentation: clarify refname disambiguation rules.Junio C Hamano, Oct 26, 2006
  11. Jakub NarebskiOct 26, 2006
  12. Josef WeidendorferOct 26, 2006
  13. Linus TorvaldsOct 26, 2006
  14. Shawn PearceOct 25, 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.