git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mostyn Bramley-Moore <mostynb@opera.com>
To: git@vger.kernel.org
Cc: Mostyn Bramley-Moore <mostynb@opera.com>
Subject: [PATCH/RFC 1/2] describe: mention glob in the --matches help text
Date: Sun, 27 Dec 2015 23:59:51 +0100	[thread overview]
Message-ID: <1451257192-5755-2-git-send-email-mostynb@opera.com> (raw)
In-Reply-To: <1451257192-5755-1-git-send-email-mostynb@opera.com>

This saves the user from needing to consult to manpage to learn the
format of the --matches argument.

Signed-off-by: Mostyn Bramley-Moore <mostynb@opera.com>
---
 builtin/describe.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/builtin/describe.c b/builtin/describe.c
index 8a25abe..2386c64 100644
--- a/builtin/describe.c
+++ b/builtin/describe.c
@@ -404,8 +404,8 @@ int cmd_describe(int argc, const char **argv, const char *prefix)
 			    N_("only output exact matches"), 0),
 		OPT_INTEGER(0, "candidates", &max_candidates,
 			    N_("consider <n> most recent tags (default: 10)")),
-		OPT_STRING(0, "match",       &pattern, N_("pattern"),
-			   N_("only consider tags matching <pattern>")),
+		OPT_STRING(0, "match",       &pattern, N_("glob"),
+			   N_("only consider tags matching <glob>")),
 		OPT_BOOL(0, "always",        &always,
 			N_("show abbreviated commit object as fallback")),
 		{OPTION_STRING, 0, "dirty",  &dirty, N_("mark"),
-- 
2.5.0

  reply	other threads:[~2015-12-27 23:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-27 22:59 [PATCH/RFC 0/2] add a perl compatible regex match flag to git describe Mostyn Bramley-Moore
2015-12-27 22:59 ` Mostyn Bramley-Moore [this message]
2015-12-27 22:59 ` [PATCH/RFC 2/2] describe: add --pcre-match option Mostyn Bramley-Moore
2015-12-27 23:39 ` [PATCH/RFC 0/2] add a perl compatible regex match flag to git describe brian m. carlson

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=1451257192-5755-2-git-send-email-mostynb@opera.com \
    --to=mostynb@opera.com \
    --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).