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

Re: describe fails on tagless branch

From
APAndy Parkins <andyparkins@gmail.com>
Date
Feb 7, 2007, 09:22 UTC
Message-ID
<200702070922.57163.andyparkins@gmail.com>
In-Reply-To
<7vr6t2g1dt.fsf@assigned-by-dhcp.cox.net>
On Wednesday 2007 February 07 02:14, Junio C Hamano wrote:
> I do not think it a good idea to make "git-describe" itself do
> the above, as the user of describe may want to fall back on
> something other than "rev-parse --verify" after ||.

Agreed - the "nearest tag" mode (--abbrev=0) would be broken in that it git-describe would return a tag that doesn't exist.

Andy
-- 
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail.com
Previous: Jakub NarebskiNext: Junio C Hamano
Message 6 of 10 in “describe fails on tagless branch”
  1. Han-Wen NienhuysFeb 7, 2007
  2. Jakub NarebskiFeb 7, 2007
  3. Han-Wen NienhuysFeb 7, 2007
  4. Junio C HamanoFeb 7, 2007
  5. Jakub NarebskiFeb 7, 2007
  6. Andy ParkinsFeb 7, 2007
  7. Junio C HamanoFeb 7, 2007
  8. Andy ParkinsFeb 7, 2007
  9. Jakub NarebskiFeb 7, 2007
  10. Junio C HamanoFeb 7, 2007

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.