git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Garry Dolley <gdolley@arpnetworks.com>
To: git@vger.kernel.org
Cc: Garry Dolley <gdolley@arpnetworks.com>, Garry Dolley <gdolley@ucla.edu>
Subject: [PATCH/RFC] Clarified how pattern works in documentation to git-show-ref.
Date: Thu, 28 Aug 2008 13:37:16 -0700	[thread overview]
Message-ID: <1219955836-10070-1-git-send-email-gdolley@arpnetworks.com> (raw)

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

             reply	other threads:[~2008-08-28 20:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28 20:37 Garry Dolley [this message]
2008-08-29  5:04 ` [PATCH/RFC] Clarified how pattern works in documentation to git-show-ref Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1219955836-10070-1-git-send-email-gdolley@arpnetworks.com \
    --to=gdolley@arpnetworks.com \
    --cc=gdolley@ucla.edu \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).