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 firstname.lastname@example.org.
Consistency between files is not obtained by simultaneous commits in CVS. It is obtained by tagging the files that belong together with a common tag value. /Bo -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Kenneth Sørensen Sent: den 15 december 2005 12:35 To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: [cvsnt] commit missing file Hi I wonder if this is the intended behavior of CVSNT? I checkout a module containing some files. Then I delete (not cvs remove) one of the files and change another one. Then I do a commit on the module to store my changes. Now I wonder - CVSNT does not complain about the missing file even if I write the command: "cvs commit <missing-file>" it will not complain or warn. In the later nothing happens. Often this will not be a problem. However, we store our compiled code in the repository together with the source. If the compiled code is deleted or missing due to some error it will not be committed together with the source code and we loose consistency between source and compiled code. Is this behavior intended and is there a way to make sure that this will not happen? We use CVSNT ver. 2.0.58d on Windows 2000 on server and client. /Kenneth _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs