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.
Doesn't the commit actually set the file back to the unedited status? Doing an extra unedit seems to be a command too many. Best regards, Bo Berglund -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Vladimir Sent: den 25 januari 2006 12:09 To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: Re: [cvsnt] Re: Strange behaviour when use commit whith '-e' option(Keep edited files) Hello Tony, >> Hello. >> >> We use commit whith '-e' option (Keep edited files). So we have faced >> with strange behaviour of cvs. >> >> When we call "cvs unedit" after successful "cvs commit -e" CVS said >> that file was changed (d_test_b.srd has been modified; revert changes?) >> When we say "yes" file rollback to prev. version (before commit >> operation). Is it expected behaviour? >> TH> Yes. Unedit rolls back to the last edit. But is it correct? IMHO This makes commit option '-e' useless. Look. It is a real situation when i do a serial of changes and after that "release" file (notify other developers that i don't edit that file anymore). So i have done many commits, but system persist that i lose my changes. And more it revert my changes back (not in a repository but in a sandbox). -- Best regards, Vladimir mailto:vab at borlas.ru _______________________________________________ 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