Hello Patrick, Thanks for your quick answer. I'm doing a checkout on a Linux box, so there is no problem with the case of files. Thanks for the tip anyway. Apparently it seems that SVN commits causing issues are the ones where the svn property "eol-style" has been changed to native (because the repositories are shared between Windows and Linux clients). I tried to reproduce this in a clean repository but I did not succeed at exhibiting the problem. Cheers, Reynald On Wed, Dec 8, 2010 at 4:36 PM, Patrick Doyle <wpdster@xxxxxxxxx> wrote: > On Wed, Dec 8, 2010 at 10:17 AM, Reynald Borer <reynald.borer@xxxxxxxxx> wrote: >> Hi again, >> >> Sorry to bother you again but I am still experiencing this problem. I >> tried with a more up to date version of Git (version 1.7.3.2), and >> this is still happening. I also tried to diagnose this issue but I am >> completely lost. >> >> I am very annoyed because this is preventing me using Git on all my >> SVN repos (2 are failing on 30...) >> >> Does anyone know how I could try to solve this issue? > > Tossing out a random theory with nothing to back it up... > > I don't know anything about the "well known checksum mismatch > problem", but are you trying to check out the SVN repository onto a > file system that is case insensitive, such as on a Windows or (default > setup) Mac host? > > If so, the repository might have files with different spellings such > as README and Readme in the same directory, which will get clobbered > on such a host. I've run into that issue in the past in a different > context. > > --wpd > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html