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

git describe fails without tags

From
Uwe Zeisberger <zeisberg@informatik.uni-freiburg.de>
Date
Jan 25, 2006, 07:47 UTC
Message-ID
<20060125074725.GA2768@informatik.uni-freiburg.de>
Hello,
using git describe on Linus' sparse repo results in:
	uzeisberger@io:~/gsrc/sparse$ git describe
	fatal: cannot describe '62ac6c16058aba8693fd5827379debc5f57b60f5'

The reason is, that there exist no tags at all, so right, there is no "most recent tag that is reachable from HEAD".

I wonder if it would be sane to assume an implicit tag for the empty repository, s.t. git describe results in

	<empty>-62ac6c16
(whatever name is choosen for <empty>).
Any opinions?

Best regards Uwe

-- 
Uwe Zeisberger

http://www.google.com/search?q=1+degree+celsius+in+kelvin
Next: Junio C Hamano
Message 1 of 7 in “git describe fails without tags”
  1. Uwe ZeisbergerJan 25, 2006
  2. Junio C HamanoJan 25, 2006
  3. Uwe ZeisbergerJan 26, 2006
  4. Junio C HamanoJan 26, 2006
  5. Uwe ZeisbergerJan 26, 2006
  6. Uwe ZeisbergerJan 26, 2006
  7. Junio C HamanoJan 26, 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.