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

Re: describe fails on tagless branch

From
Jakub Narebski <jnareb@gmail.com>
Date
Feb 7, 2007, 00:40 UTC
Message-ID
<eqb73j$hri$1@sea.gmane.org>
In-Reply-To
<eqb660$ft7$1@sea.gmane.org>
[Cc: git@vger.kernel.org]
Han-Wen Nienhuys wrote:
Show 19 quoted lines
> try 
> 
>   git init
>   echo hoi > a
>   git add a
>   git commit -m 'add a' a
>   git describe
> 
> this yields
> 
> 
> [lilydev@haring t]$ git describe
> fatal: cannot describe '3b26396bbb5f18580ffd4bc31f70ef0738ec73d6'
> 
> 
> I would prefer it if an implicit tag INIT was supposed at the start of the
> history, so we'd get
> 
>   INIT-3b2...

_Which_ INIT? In git there can be more than one root commit. In git.git repository mainline (maint, master, next and pu branches) has 4 roots (plus three linear independent branches: man, html and todo, each with its own root).

I agree that error description should probably be better: cannot describe _why_.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Previous: Han-Wen NienhuysNext: Han-Wen Nienhuys
Message 2 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.