git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[gitk] searching misses relevant commits

From
LBLyndon Brown <jnqnfe@gmail.com>
Date
Aug 31, 2020, 05:08 UTC
Message-ID
<14a46bcf8da119af8b8882fe77a0d96ff3984b1a.camel@gmail.com>
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
Message 1 of 1 in “[gitk] searching misses relevant commits”
  1. Lyndon BrownAug 31, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.