-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12-07-06 2:28 AM, H Brydon wrote: > I have a new problem with cvs where it is not committing or > updating my files correctly. [...] > Two questions: (1) What is wrong with my sandbox and/or repository? > Hopefully this is a known problem with a simple solution. It's difficult to say without more information. Can you post the sequence of commands you used to reproduce the problem in your test directory?
> (2) Are the day's file changes truly lost or are they hiding > somewhere? There should be a file in your working directory with same name as your original file, prefixed with .#, and with the original file's version number appended to it. For example, if the file name is afile.txt and it was revision 1.4, the saved file would be .#afile.txt.1.4 However, if the .# file already exists, CVS will overwrite it. Since you've repeatedly updated and tried committing, the original file may now be lost. - -- Jim Hyslop Dreampossible: Better software. Simply. http://www.dreampossible.ca Consulting * Mentoring * Training in C/C++ * OOD * SW Development & Practices * Version Management -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/21kEACgkQLdDyDwyJw+PvjQCg/DZqnSxVoTxkMjTX6oC2syuQ iIMAoIZGFg7evtAIrZLNohhQ/cnWUyPp =hi6r -----END PGP SIGNATURE-----
