Add a perl-compatible regular expression version of the --match option,
which allows more flexible pattern matching.
Signed-off-by: Mostyn Bramley-Moore
---
Documentation/git-describe.txt | 5 +++
builtin/describe.c | 69 ++
t/README
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
This saves the user from needing to consult to manpage to learn the
format of the --matches argument.
Signed-off-by: Mostyn Bramley-Moore
---
builtin/describe.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/builtin/describe.c b/builtin/describe.c
index 8a25abe..2386c64
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
This allows more flexible pattern matching than the default globs.
Signed-off-by: Mostyn Bramley-Moore
---
Documentation/git-describe.txt | 15 +--
builtin/describe.c | 90 +-
t/README | 3 +-
t/t6120-describe.sh
Signed-off-by: Mostyn Bramley-Moore
---
Documentation/git-describe.txt | 6 ++
builtin/describe.c | 41 +
t/t6120-describe.sh| 14 ++
3 files changed, 61 insertions(+)
diff --git a/Documentation/git-describe.txt b
On 12/28/2015 09:30 PM, Junio C Hamano wrote:
Mostyn Bramley-Moore writes:
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
On 12/29/2015 07:27 PM, Junio C Hamano wrote:
Mostyn Bramley-Moore writes:
I do not think it is wrong per-se to add an option to use regular
expressions instead of globs, but if we are to do so, the endgame we
aim for MUST be that we do so consistently to all the other commands
that iterate
describe searches. But perhaps I misunderstand what you're suggesting
with the backquote/subshell.
-Mostyn.
--
Mostyn Bramley-Moore
TV and Connected Devices
Opera Software ASA
most...@opera.com
--
To unsubscribe from this list: send the line "unsubscribe git" in
the bo
On 12/31/2015 01:23 AM, Junio C Hamano wrote:
Mostyn Bramley-Moore writes:
OK, brainstorming a bit, how about either of these:
1)
--match-pattern-type=
It's a bit lengthy (maybe --match-type would be sufficient), but I
like that the value names are shared with git grep etc option names
On 01/04/2016 06:46 PM, Junio C Hamano wrote:
Mostyn Bramley-Moore writes:
On 12/31/2015 01:23 AM, Junio C Hamano wrote:
...
Swapping the option key and value may not be a bad idea, but one
problem that the above does not solve, which I outlined in the
message you are responding to, is that
List the fields in order of appearance in the command output.
Signed-off-by: Mostyn Bramley-Moore
---
Documentation/git-ls-files.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-ls-files.txt b/Documentation/git-ls-files.txt
index 1cab703..a9149fc
List the fields in order of appearance in the command output.
Signed-off-by: Mostyn Bramley-Moore
---
Documentation/git-ls-files.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-ls-files.txt b/Documentation/git-ls-files.txt
index 1cab703..d153c17 100644
13 matches
Mail list logo
