* [gitk] searching misses relevant commits
@ 2020-08-31 5:08 Lyndon Brown
0 siblings, 0 replies; only message in thread
From: Lyndon Brown @ 2020-08-31 5:08 UTC (permalink / raw)
To: git
Hi,
When searching commits (by which I mean the "find" feature), sometimes
relevant entries are missed which should have been selected. I reported
this to Debian as bug #969197 ([1]).
I gave an example in the Debian bug report of searching the VLC
codebase for commits adding/removing "set_capability" (exact; all
fields). While 888451fe5146a49de8d49e830dbe57dd478e358f was one of
those found, the adjacent
commit 46650ad3f7f92d2757c43b42aa170965dc1df25c was skipped, despite it
being entirely relevant.
Changing to IgnCase makes no difference.
I'm a Debian Linux user, running version 1:2.28.0-1.
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969197
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-08-31 5:08 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-31 5:08 [gitk] searching misses relevant commits Lyndon Brown
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).