summaryrefslogtreecommitdiff
path: root/Documentation/config/clone.txt
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2021-12-05 12:26:16 -0800
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-12-05 12:26:43 -0800
commit91028f7659c165eb48910d333a78e4dac9cff2b6 (patch)
tree21ca8a3a57428980680e474e3bd3d87e71dff789 /Documentation/config/clone.txt
parentGit 2.34.1 (diff)
downloadtgif-91028f7659c165eb48910d333a78e4dac9cff2b6.tar.xz
grep: clarify what `grep.patternType=default` means
We documented that with grep.patternType set to default, the "git grep" command returns to "the default matching behavior" in 84befcd0 (grep: add a grep.patternType configuration setting, 2012-08-03). The grep.extendedRegexp configuration variable was the only way to configure the behavior before that, after b22520a3 (grep: allow -E and -n to be turned on by default via configuration, 2011-03-30) introduced it. It is understandable that we referred to the behavior that honors the older configuration variable as "the default matching" behavior. It is fairly clear in its log message: When grep.patternType is set to a value other than "default", the grep.extendedRegexp setting is ignored. The value of "default" restores the current default behavior, including the grep.extendedRegexp behavior. But when the paragraph is read in isolation by a new person who is not aware of that backstory (which is the synonym for "most users"), the "default matching behavior" can be read as "how 'git grep' behaves without any configuration variables or options", which is "match the pattern as BRE". Clarify what the passage means by elaborating what the phrase "default matching behavior" wanted to mean. Helped-by: Johannes Altmanninger <aclopte@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/config/clone.txt')
0 files changed, 0 insertions, 0 deletions