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

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

From
Garry Dolley <gdolley@arpnetworks.com>
Date
Aug 28, 2008, 20:37 UTC
Message-ID
<1219955836-10070-1-git-send-email-gdolley@arpnetworks.com>

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?

This is my first patch, I tried to follow all the rules in the SubmittingPatches doc. If I missed anything, I apologize.

 Documentation/git-show-ref.txt |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-show-ref.txt b/Documentation/git-show-ref.txt
index 2f173ff..5966450 100644
--- a/Documentation/git-show-ref.txt
+++ b/Documentation/git-show-ref.txt
@@ -86,7 +86,8 @@ OPTIONS
 
 <pattern>...::
 
-	Show references matching one or more patterns.
+	Show references matching one or more patterns. The pattern is tail-matched,
+	achored on a '/' boundary; pattern does not accept globs.
 
 OUTPUT
 ------
@@ -127,7 +128,8 @@ use:
 -----------------------------------------------------------------------------
 
 This will show "refs/heads/master" but also "refs/remote/other-repo/master",
-if such references exists.
+if such references exists. This will not match "refs/heads/master2", because
+the pattern is tail-matched.
 
 When using the '--verify' flag, the command requires an exact path:
 
-- 
1.6.0.1
Next: Junio C Hamano
Message 1 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.