I'm genuinely surprised that this doesn't seem to have been reported, but I swear I did my homework searching in Google, in this users list, and in the Git Community Mailing List, without relevant results. So, here it goes.
Gitk "find commit" search function doesn't follow the "IgnCase" option that is selectable with a combo selector on the right side of the window; it should be searching in a case-insensitive way, but it doesn't. Steps to reproduce: 1. Clone any repo. I'm right now using https://github.com/Kurento/kms-core.git 2. cd into the repo and launch gitk 3. In the "Find commit" bar, select "changing lines matching" 4. In the right side of the same bar, select "IgnCase" 5. Search for a term that you know exists in uppercase, but write the search in lowercase. In my example, I'm searching for "leaky_time". 6. No search results appear. 7. Change your search word to uppercase. 8. Some search results appear, thus proving that the search is being done case-sensitive. The only direct mention of this issue that I was able to find was this answer that seems to confirm that this is a bug, but doesn't help much: https://stackoverflow.com/questions/11964704/msysgit-how-do-i-use-gitk-to-search-for-string-in-commit-ignoring-case Should I follow steps from https://git-scm.com/community and write a bug report directly to the Git mailing list? Or maybe this is well known and the solution is hidden somewhere here? -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
