Menu
▾
▴
#47 Added display of current editors of item
... just like in SourceSafe I've added the display of who
is currently
editing which file. There are also two minor fixes
regarding crashes on init
time when it calls a method on a NULL pointer - at least
in the debug
version it did.
------- Additional Comments From Martin Hoffesommer
2000-06-14 15:33 -------
Created an attachment (id=20)
WinCvs diff #1
------- Additional Comments From Martin Hoffesommer
2000-06-14 15:33 -------
Created an attachment (id=21)
WinCvs diff #2
------- Additional Comments From Jerzy 2000-07-26
04:27 -------
Hm... How does it work in offline? Because unlike
SourceSafe, in CVS you don't
have to be connected to the server to start modify the
file, nor you have to do
edit before you start modifications...
The other question is 'why would you care?'. Up until the
commit time you don't
care who is editing what, you only care about your own
changes. Then, during
the commit you still don't care, unless you run into
conflict. But then again,
you don't care who is editing the file, but who commited
the changes to the
same file before you did, only when you get the conflict.
You can use 'editors' and wathes to see if the file is
potentially modified by
others, but from my experience it is not very useful 99%
of the time.
Logged In: NO
Reporter: mh@soft-enterprises.com (Martin Hoffesommer)
Logged In: YES
user_id=5362
"Up until the commit time you don't care who is editing what"
Thats not always true, it really depends on your internal
development structure. Sometimes diff/merge conflict
resolution is more of a waste of time then having single
person at a time editing per file.
Most of the time cvs works fine as is, but there are times
when the other way works better.