[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Any recommendations on best practices to help non-developers withCV
Re: Any recommendations on best practices to help non-developers withCVS?
Tue, 07 Dec 2004 14:33:34 -0500
Denis Haskin wrote:
> I've started introducing some of the business people to CVS (using
> TortoiseCVS and other client-side tools) and they've got some pretty
> serious reservations.
> The biggest one (as you might expect) is the optimistic locking model.
> Given that more (most?) of their files are going to be binary, not text,
> the fact that there's no locking on checkout gives them the willies. Is
> there any way to address this? I've looked a bit at watch/edit/unedit,
> but it's unclear to me whether that would really address their
> concerns. Any comments?
> Any other way to address this?
CVSNT has merged in the "Reserved Edits" patch, although it is still an
advisory lock, it requires the user to pass an option to bypass it (if they
have -c in their .cvsrc file IIRC). If a user bypasses it with out good
reason then you are back to the same situation you had with VSS when someone
would grab a copy from somewhere and start editing it (actually you are in a
better situation, you know where their copy came from with cvs), i.e.,
appropriately sized cluebat.
Another way would be to help finish the merge of "Reserved Edits" (was
"advisory locks" or "edit -c" in the archive of this list) into the cvshome
version (if it is not already done). This would be the same thing (I think)
as CVSNTs "Reserved Edits" above.
*Mark*, I did not see this listed in the release notice for 1.12.10, how
goes the work?
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter