Package: gitk Version: 1:2.28.0-1 Severity: important Sometimes when I use the search functionality in gitk, it misses commits.
For example, just right now I am rebasing some work I did for the VLC codebase. I had a need to search for all commits adding/removing the string "set_capability". It is important that I find all commits with this so that I can find relevant changes to reflect in my rebased work. This search found commit 66c7fc04d7d0d944215c99012cbcb94dc42c3531 for instance. Another was 888451fe5146a49de8d49e830dbe57dd478e358f, though this is unhelpful since it involves renaming files (it would be much better if gitk excluded such commits), but then crucially missed the commit after that - 46650ad3f7f92d2757c43b42aa170965dc1df25c - which most definitely is relevant. An accurate search is crucially important. I have literally thousands of commits to rebase this work upon to catch up before resubmitting it, including some very large commits, and having the search facility miss commits like this is not at all helpful. FYI, I have encountered this numerous times in the past, but was only now frustrated enough to bother reporting it. Please fix it :)
