[ On Monday, June 18, 2001 at 14:39:53 (-0700), Kostur, Andre wrote: ]
> Subject: RE: Future CVS Development
>
> Granted, if the user chooses to circumvent the source code control system,
> you're in trouble, and that's where merge becomes useful as a safety net.
> But if CVS could enforce that a user declares their edits before allowing
> them to commit to the repository (OK, for files declared as COPY, and -kb
> files. Ones where CVS cannot automatically handle conflicts), this would
> allow people to checkout a copy of the repository without blocking anybody,
> but not allowing them to edit the binary files without notifying the
> repository.
But CVS doesn't WANT such a capability! It's contrary to the core design!
If you can't handle concurrent editing of non-text/non-mergable files
then DON'T USE CVS!!!!!
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
