From: Mostyn Bramley-Moore <mostynb@opera.com>
To: git@vger.kernel.org
Cc: Mostyn Bramley-Moore <mostynb@opera.com>,
"brian m . carlson" <sandals@crustytoothpaste.net>
Subject: [PATCH/RFC v2 0/2] add regex match flags to git describe
Date: Mon, 28 Dec 2015 11:30:22 +0100 [thread overview]
Message-ID: <cover.1451298323.git.mostynb@opera.com> (raw)
git describe currently only supports glob matching with the --matches flag.
It would be useful to support regular expressions.
For consistency, this uses the same regex flags as those used by git-grep.
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.
Mostyn Bramley-Moore (2):
describe: add option to use perl-compatible regexes with --match
describe: add basic and extended posix regex matching for completeness
Documentation/git-describe.txt | 21 ++++++-
builtin/describe.c | 131 ++++++++++++++++++++++++++++++++++++++++-
t/README | 3 +-
t/t6120-describe.sh | 38 ++++++++++--
4 files changed, 184 insertions(+), 9 deletions(-)
--
2.5.0
next reply other threads:[~2015-12-28 10:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 10:30 Mostyn Bramley-Moore [this message]
2015-12-28 10:30 ` [PATCH/RFC v2 1/2] describe: add option to use perl-compatible regexes with --match Mostyn Bramley-Moore
2015-12-28 10:30 ` [PATCH/RFC v2 2/2] describe: add basic and extended posix regex matching for completeness Mostyn Bramley-Moore
2015-12-28 20:30 ` [PATCH/RFC v2 0/2] add regex match flags to git describe Junio C Hamano
2015-12-29 0:13 ` Mostyn Bramley-Moore
2015-12-29 18:27 ` Junio C Hamano
2015-12-30 9:52 ` Duy Nguyen
2015-12-31 0:08 ` Mostyn Bramley-Moore
2015-12-31 0:00 ` Mostyn Bramley-Moore
2015-12-31 0:23 ` Junio C Hamano
2015-12-31 10:07 ` Mostyn Bramley-Moore
2016-01-04 17:46 ` Junio C Hamano
2016-01-06 1:08 ` Mostyn Bramley-Moore
2016-01-06 12:23 ` Duy Nguyen
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=cover.1451298323.git.mostynb@opera.com \
--to=mostynb@opera.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.