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

Re: git describe is failing

From
ESEugene Sajine <euguess@gmail.com>
Date
Oct 22, 2009, 15:10 UTC
Message-ID
<76c5b8580910220810n389d065di349339ab38909ef7@mail.gmail.com>
In-Reply-To
<200910221702.39452.trast@student.ethz.ch>
Show 17 quoted lines
> man git-describe:
>
> DESCRIPTION
>       The command finds the most recent tag that is reachable from a
>       commit.
> [...]
>       By default (without --all or --tags) git describe only shows
>       annotated tags. For more information about creating annotated
>       tags see the -a and -s options to git-tag(1).
>
> If there is no such tag, it refuses to work.  Annotate your tags, or
> try --always.
>
> --
> Thomas Rast
> trast@{inf,student}.ethz.ch
>

Thanks! It is working ok. Although it is probably not the best error handling. I believe git should fail with some meaningful message in this case...

Thanks, Eugene

Previous: Thomas RastNext: Thomas Rast
Message 4 of 13 in “git describe is failing”
  1. Eugene SajineOct 22, 2009
  2. Mikael MagnussonOct 22, 2009
  3. Thomas RastOct 22, 2009
  4. Eugene SajineOct 22, 2009
  5. describe: when failing, tell the user about options that workThomas Rast, Oct 22, 2009
  6. Alex RiesenOct 22, 2009
  7. Junio C HamanoOct 22, 2009
  8. Nicolas PitreOct 23, 2009
  9. Junio C HamanoOct 23, 2009
  10. Junio C HamanoOct 23, 2009
  11. Thomas RastOct 23, 2009
  12. Junio C HamanoOct 23, 2009
  13. describe: when failing, tell the user about options that workThomas Rast, Oct 28, 2009

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.