[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #21023] Possible commit problem

From: Todd Denniston
Subject: [bug #21023] Possible commit problem
Date: Fri, 14 Sep 2007 23:18:40 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20070713 Firefox/

Follow-up Comment #2, bug #21023 (project cvs):

Re comment #1
There are other problems with having an editor open with a CVS controlled
file than just this window of oportunity for the date to get funky.
The biggest I know of is that if the user happens to change the editor buffer
after issuing the `cvs commit` (or gui equivalent), and then saves the result,
the user will loose any changes that may have been merged in by CVS from other
users checking in, i.e., when CVS is used in it's CONCURRENT mode of

The ONLY sane things to do are:
1) educate the users that they _will_ at some point cause one another (not
just themselves) to loose changes that others put into CVS, and the other
coder may not be happy about it & the boss will NOT be happy about it.  (the
loss can be fixed with a `cvs -jr1 -jr2` where r1=r2 - 1rev  and r2=rev before
loss, but don't tell them that).
2) make it company/group/project policy to discipline (publicly if necessary)
anyone who has an editor open while running CVS commands.

Summary: the problem you see is only the very tip of the iceberg created by
having a CVS controled file open in an editor while also running a CVS commit
_OR_ update command.  I doubt I am alone in seeing this as a user education
problem, but I am going to leave the bug open. 


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]