[gitk] searching misses relevant commits

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux