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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 19, 2014, 19:10 UTC
Message-ID
<xmqq38f0hg0h.fsf@gitster.dls.corp.google.com>
In-Reply-To
<87d2e4d8w7.fsf@osv.gnss.ru>
Sergei Organov <osv@javad.com> writes:
> Will something break if it won't helpfully prepend refs/tags/ once
> --all is given?

"describe --all --match 'v*'" will no longer match a tag v1.2.3, and forces the users to say "describe --match 'refs/tags/v*'", and these users will probably see it as a new breakage, I would imagine.

Previous: Sergei OrganovNext: Sergei Organov
Message 4 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.