Stephen, (not cross posting to meld-list).
The most common practice is to ignore this as a side-effect. TortoiseCVS and WinCVS simply don't warn users that such a thing may happen, and I've been following those mailing lists for some time and never seen it complained about. If you care particularly you can make the location of the CVS/CVSNT client executable a user preference so that people who know (and care) about the difference can make that choice. The 'updating' of formats that CVSNT does has no effect on the backwards compatibility with CVS, so there is no down side really (basically CVSNT adds some extra control files like CVS/Entries.Extra, which CVS 1.11 or 1.12 will just ignore). Exactly the same rules apply with EVS clients (except the added control files are all XML like CVS/Entries.XML). I strongly recommend that if you are beginning work on integrating with CVSNT that you stop and switch to EVS (previously known as CVSNT 3.1), see evscm.org. Regards, Arthur Barrett -----Original Message----- From: [email protected] on behalf of Stephen Kennedy Sent: Sun 3/22/2009 1:59 AM To: [email protected] Cc: meld-list Subject: [cvsnt] Detect a cvsnt vs cvs working copy? Is it possible to detect a cvsnt vs cvs working copy? The faq says that invoking cvsnt in a cvs working copy will update the files to cvsnt format.[1] I'm writing a working copy viewer, meld[2] and wouldn't want that change to happen as a side effect. Stephen. [1] http://www.march-hare.com/cvspro/faq/faq1.asp#1i [2] http://meld.sf.net _______________________________________________ cvsnt mailing list [email protected] http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt Upgrade to CVS Suite for more features and support: http://march-hare.com/cvsnt/ _______________________________________________ cvsnt mailing list [email protected] http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt Upgrade to CVS Suite for more features and support: http://march-hare.com/cvsnt/
