I'm having problems using git-cvsserver to support a wincvs user. It seems to be truncating binary files in both directions (e.g., we have a PNG that starts, in hex, 89 50 4e 47 0d 0a ..., and it gets truncated between the 0d and 0a), and it seems to fail up-to-date checks when checking in files that are, in fact, up-to-date (and, so far as I can see, haven't been modified anywhere else). I haven't tried much with this repository, but at least the binary file commit and update worked for me with real cvs. The user is using WinCvs 1.3.13.2 Beta 13 (Build 2), which seems to be the version he could find at the time that would talk to both their local CVS server and sourceforge. The user doesn't have any of these problems talking to a real cvs server. Anybody got any experience with wincvs and cvsserver, or any idea how things could be different between git-cvsserver and real cvs? He's presently going to use his own version control and just send us results, but it would be nice if this could be magically worked out before we started working together closely again in a couple of weeks. -Daniel *This .sig left intentionally blank* - 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