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

Re: [PATCH] t6300: avoid creating refs/heads/HEAD

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 27, 2017, 21:44 UTC
Message-ID
<xmqqefyjnwat.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<xmqqshmzuyam.fsf@gitster.mtv.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
> ...  I suspect that calling interpret_empty_at() from
> that function is fundamentally flawed.  The "@" end user types never
> means refs/heads/HEAD, and HEAD@{either reflog or -1} would not mean
> anything that should be taken as a branch_name, either.  
The latter should read "HEAD@{either reflog or -1 or 'upstream'}"

Or do we make HEAD@{upstream} to mean "deref HEAD to learn the current branch name and then take its upstream"? If so @@{upstream} might logically make sense, but I do not see why @{upstream} without HEAD or @ is not sufficient to begin with, so...

Previous: Junio C HamanoNext: Jeff King
Message 7 of 8 in “t6300: avoid creating refs/heads/HEAD”
  1. t6300: avoid creating refs/heads/HEADJeff King, Feb 27, 2017
  2. Junio C HamanoFeb 27, 2017
  3. Jeff KingFeb 27, 2017
  4. Junio C HamanoFeb 27, 2017
  5. Jeff KingFeb 27, 2017
  6. Junio C HamanoFeb 27, 2017
  7. Junio C HamanoFeb 27, 2017
  8. Jeff KingFeb 27, 2017

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.