Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
Jan, > Probably a job matches a commitId (although I haven't looked into > commitId's yet). Yes from the sounds of it that is exactly what you should be using. And yes - if you want to 'rollback' a commit you certainly can using the commit id. cvs update -e -j @commitid -j "@<commitid" When you commit this a mergepoint will also be creating which shows in the history that the change was rolled back. Note: there are also 'user defined changesets' which can span multiple commits, see "cvs commit -B jub-number". > Anything that's committed is automatically immediately compiled and > query's are automatically checked for proper index usage. And that's exactly what the 'build' plugin in CVS Suite (the commercially supported version of CVSNT) is used for. In the latest version of this we also pass the 'user defined job number' but I've never thought of the need to pass the 'commitid' - but it'd be easy enough to add... Regards, Arthur Barrett