0

I'm sure this question seems really simple. I have a git repository and I am reviewing it in gitk. There is an option to:

Find Next prev commit adding/removing string: some string IgnCase All fields

There are commits that contain Some String (exactly as I just cased it) and if I search for it exactly as cased gitk will show the matches. However if I search as I did above using some string then there are no matches. Maybe it's late and I'm tired but why doesn't that work? Does anyone here use msysgit? I'm using git version 1.7.11.msysgit.1.

Thanks

loop
  • 3,460
  • 5
  • 34
  • 57

1 Answers1

1

gitk internally calls git diff-tree -S<string> in that case, which performs a case sensitive search. In fact, git diff-tree seems to even accept a (somewhat undocumented) "-i" option to ignore the case, but gitk does not make use of that. In short, it's a bug in gitk as it should either disable "IgnCase" when searching added / removed strings or make use of "-i".

sschuberth
  • 28,386
  • 6
  • 101
  • 146