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.
Brian Smith wrote: > > So, do you want a hash for each revision or for the file as a whole? I > am thinking that a single hash for the file would be sufficient. > A hash for each version would be useful. If you take a hash of the complete file before checkin (I think cvs already does this) then store it, when you reconstruct the file for checkout you can verify that the checkout is working correctly as well (no bugs in the diff algorithm, etc.) Tony _______________________________________________ Cvsnt mailing list Cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs