Hello, A colleague of mine is using TortoiseCVS to access git-cvserver on my system to do development on Windows with a repository stored on my machine. It's all gone fairly well, nice and easy to use. However, we've found that images stored in the repository are being corrupted on checkout to the Windows machine. Even though they are binary files, they're having the line endings rewritten (in a really strange way as well). I don't think git itself is at fault; the source files are all retaining their original unix line endings, and the images are uncorrupted when I check them out. I've done a bit of research though and found that CVS marks binary files in the repository, not in the client, so I assume that git-cvsserver is at fault. It's telling the client side that the image files are text. To be as close to git as possible, I reckon that git-cvsserver should be telling the remote that /every/ file is binary and leave the line endings alone (although that would perhaps annoy some windows users). I'd much prefer it if what was checked out was what was checked in. I'm at a bit of a loss as to how to do it though. I don't know enough about the CVS protocol to know which part of git-cvsserver is telling the client the file type. Should I even try to make all binary checkouts via CVS or should I try and use the auocrlf work that's going on now? Andy -- Dr Andy Parkins, M Eng (hons), MIET andyparkins@xxxxxxxxx - 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