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

Re: [PATCH/RFC] Clarified how pattern works in documentation to git-show-ref.

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 29, 2008, 05:04 UTC
Message-ID
<7vtzd48l8x.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<1219955836-10070-1-git-send-email-gdolley@arpnetworks.com>
Garry Dolley <gdolley@arpnetworks.com> writes:
Show 13 quoted lines
> Several people in #git, including myself, thought that the following would
> show all refs:
>
>   git show-ref '*'
>
> Since that is not how the pattern patching works, clarification was needed
> in the documentation.
>
> Signed-off-by: Garry Dolley <gdolley@ucla.edu>
> ---
>
> I think including a little more info in the docs regarding the pattern would
> be helpful.  Comments?
Would be helpful.

It may be worthwhile to know that that "pathspec" limiting done by revision traversal ("git log", "git rev-list") and diff is also without globbing, but it is a head-match, and match is forced at '/' boundary.

ls-files and grep know how to glob, on the other hand.
Previous: Garry Dolley
Message 2 of 2 in “Clarified how pattern works in documentation to git-show-ref.”
  1. Clarified how pattern works in documentation to git-show-ref.Garry Dolley, Aug 28, 2008
  2. Junio C HamanoAug 29, 2008

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.