Duy Nguyen [off-list ref] writes:
I was careless and checked the wrong variable (should have checked
nr_duplicates not state.nr_duplicates; the second is a pointer). So we
always get this warning (and with no following list of files)
Heh, does that bug go away if you got rid of the pointer-ness of the
field and store the value directly in there?
quoted
I also notice that this patch doesn't add any tests... :)
This is platform specific and I was to be frank a bit lazy. Will
consider adding a test with CASE_INSENSITIVE_FS after this.