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 0/2] add a perl compatible regex match flag to git describe
Date: Sun, 27 Dec 2015 23:59:50 +0100	[thread overview]
Message-ID: <1451257192-5755-1-git-send-email-mostynb@opera.com> (raw)

git describe currently only supports glob matching with the --matches flag.
It would be useful to support regular expressions.

PCRE is already an optional dependency from git grep, I wonder if posix or
extended regexes would be preferable?

Some old discussion of this as a candidate feature is here, though nobody put
together a patch as far as I can see:
http://comments.gmane.org/gmane.comp.version-control.git/173873

Mostyn Bramley-Moore (2):
  describe: mention glob in the --matches help text
  describe: add --pcre-match option

 Documentation/git-describe.txt |  5 +++
 builtin/describe.c             | 73 ++++++++++++++++++++++++++++++++++++++++--
 t/README                       |  3 +-
 t/t6120-describe.sh            | 29 ++++++++++++++---
 4 files changed, 103 insertions(+), 7 deletions(-)

-- 
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 Mostyn Bramley-Moore [this message]
2015-12-27 22:59 ` [PATCH/RFC 1/2] describe: mention glob in the --matches help text Mostyn Bramley-Moore
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-1-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).