GNU bug report logs - #36644
Git log search

Previous Next

Full log

View this message in rfc822 format

From: Juri Linkov <juri <at> linkov.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: rpluim <at> gmail.com, 36644 <at> debbugs.gnu.org, Dmitry Gutov <dgutov <at> yandex.ru>
Subject: bug#36644: Git log search
Date: Thu, 25 Jul 2019 22:00:36 +0300

>> > I also see your point: it would be nice to be able to document the
>> > semantics of PATTERN in a backend-independent way.  But I think this
>> > is next to impossible in this case, both because of significant
>> > differences in the backend capabilities (e.g., bzr doesn't have the
>> > equivalent of Git's --fixed-strings, AFAICT), and because some backend
>> > allow great flexibility in interpreting PATTERN, under control of
>> > optional switches passed to the backend.
>>
>> The other option is to standardize on basic or extended regexp, and
>> simply give up for backends that can't support that.
>
> We could simply say "regular expression" and leave the details
> unspecified.  But I think Juri said that fixed strings was the lowest
> common denominator, which is why I proposed a slightly more vague doc
> string.  Juri, which backends don't support regular expressions?

The documentation of 'git-log' uses the term 'pattern' for a good reason
since it covers all possible values: basic-regexp, extended-regexp,
perl-regexp, fixed-strings.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.