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

Surprising 'git-describe --all --match' behavior.

From
SOSergei Organov <osv@javad.com>
Date
Jun 19, 2014, 13:31 UTC
Message-ID
<87ionxxbz8.fsf@osv.gnss.ru>
Hello,
Just playing with it, got some surprises:

$ git --version git version 1.9.3

$ git describe --all heads/v3.5 $ git describe --all --match 'v*' tags/v3.5.6b2-4-gab4bf78 $ git describe --all --match 'heads/v*' fatal: No names found, cannot describe anything.

... "heads/v3.5" matches neither 'v*' nor 'heads/v*'?

$ git describe --all --match 'v*' tags/v3.5.6b2-4-gab4bf78 $ git describe --all --match 'tags/v*' fatal: No names found, cannot describe anything.

... git matches short names when outputs full names?
Is it a defect, or what do I miss?
-- 
Sergei.
Next: Junio C Hamano
Message 1 of 6 in “Surprising 'git-describe --all --match' behavior.”
  1. Sergei OrganovJun 19, 2014
  2. Junio C HamanoJun 19, 2014
  3. Sergei OrganovJun 19, 2014
  4. Junio C HamanoJun 19, 2014
  5. Sergei OrganovJun 19, 2014
  6. Junio C HamanoJun 19, 2014

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.