On Thu, May 28, 2015 at 9:20 PM, Junio C Hamano gits...@pobox.com wrote:
SZEDER Gábor sze...@ira.uka.de writes:
@@ -16,11 +16,12 @@ SYNOPSIS
'git config' [file-option] [type] [-z|--null] --get-all name [value_regex]
'git config' [file-option] [type] [-z|--null] --get-regexp name_regex
On Fri, May 29, 2015 at 01:34:50PM +0200, Christian Couder wrote:
+--get-name-regexp::
+ Like --get-regexp, but shows only matching variable names, not its
+ values.
which makes it clear why it is needed. The distinction is purely
about the output, i.e. the values are
Junio C Hamano gits...@pobox.com writes:
The 'type' may also be shared between these two options, no? It
would be logically consistent if you can say
git config --bool --get-name-regexp '.*' 'no'
to find all configuration variables that are set to 'false' in
different spellings like
SZEDER Gábor sze...@ira.uka.de writes:
@@ -16,11 +16,12 @@ SYNOPSIS
'git config' [file-option] [type] [-z|--null] --get-all name [value_regex]
'git config' [file-option] [type] [-z|--null] --get-regexp name_regex
[value_regex]
'git config' [file-option] [type] [-z|--null] --get-urlmatch
Recenty I created a multi-line branch description with '.' and '='
characters on one of the lines, and noticed that fragments of that line
show up when completing set variable names for 'git config', e.g.:
$ git config --get branch.b.description
Branch description to fool the completion
5 matches
Mail list logo
