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 sales@march-hare.com.
On Thu, 06 Mar 2003 22:27:48 +0000, Tony Hoyle <tmh at nodomain.org> wrote: >Bo Berglund wrote: > > >> I never saw suct behaviour before, what is going on here? >> I have not put any locks anywere and it was a month or so since I did >> anythin at all in this test module. ????????????? > >It's possible the module was being checked out at the time, unless there's a >dangling lock in the directory. > >btw. I've fixed the file undelete to be more sane now... > >Was: > > >$ cvs add test >cvs server: re-adding file test (in place of dead revision 1.2) >cvs server: use 'cvs commit' to add this file permanently >$ cvs update test >cvs server: warning: new-born test has disappeared <-- DOH!!! > >Now: > >$ cvs add test >cvs server: re-adding file test (in place of dead revision 1.4) >cvs server: use 'cvs commit' to add this file permanently >$ cvs update test >cvs server: resurrecting deleted file test >U test > >.. which is much more sane behviour IMHO. > >Tony > What happened to the cvs commit step? Is it not necessary? And does the client cvs.exe need to be updated to make this work, or is it sufficient to put a new version on the server? (I got the new source from CVS, just asking out of curiosity...) /Bo (Bo Berglund, developer in Sweden)