{"thread":{"id":"54165","subject":"[gitk] searching misses relevant commits","startedAt":"2020-08-31T05:08:19Z","lastAt":"2020-08-31T05:08:19Z","messageCount":1,"participants":["Lyndon Brown"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"404785","messageId":"14a46bcf8da119af8b8882fe77a0d96ff3984b1a.camel@gmail.com","threadId":"54165","inReplyTo":null,"subject":"[gitk] searching misses relevant commits","fromName":"Lyndon Brown","fromEmail":"jnqnfe@gmail.com","sentAt":"2020-08-31T05:08:12Z","receivedAt":"2020-08-31T05:08:19Z","isPatch":false,"sender":{"key":"jnqnfe@gmail.com","avatar":null},"body":"Hi,\n\nWhen searching commits (by which I mean the \"find\" feature), sometimes\nrelevant entries are missed which should have been selected. I reported\nthis to Debian as bug #969197 ([1]).\n\nI gave an example in the Debian bug report of searching the VLC\ncodebase for commits adding/removing \"set_capability\" (exact; all\nfields). While 888451fe5146a49de8d49e830dbe57dd478e358f was one of\nthose found, the adjacent\ncommit 46650ad3f7f92d2757c43b42aa170965dc1df25c was skipped, despite it\nbeing entirely relevant.\n\nChanging to IgnCase makes no difference.\n\nI'm a Debian Linux user, running version 1:2.28.0-1.\n\n[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969197\n\n"}]}