Is it good practice to add *.xml -kb to cvswrappers so that XML files are treated as binary to prevent CVS from trying to merge xml documents together?
Visual Studio produces many machine generated configuration files as XML documents, so nobody really ever looks at these. If they get checked into CVS, and a merge occurs, I can see CVS adding multiple occuring sub-elements where only one should occur. This could potentially break conformance to a schema. I also could see nobody realizing a merge conflict occured in an XML document. The <<<<<<<<<<<<<<< that CVS puts in to highlight a conflict won't help the XML parser output a meaningful error message. Andy
