Well, I think the darcs concept is centered on avoiding the whole check-out system. Also, I'm not sure I see how such an option could be implemented within darcs. Since there's no check-out process, darcs would be reduced to warning that two users had modified the file in parallel -- implying that the files ought to be checked for the sort of undetectable semantic conflict you proposed.
Regards, Ralph On 1/15/07, Kauker, Hubert <[EMAIL PROTECTED]> wrote:
Ralph, > That's an interesting point. I'm sure this is one reason why typical > source control systems don't allow two developers to work on one file > at the same time. Would it be reasonable for darcs to have an option to support such "typical" behavior, too? > But consider that the same sort of thing could happen even if two > developers were working on two different files -- call them fileA and > fileB. Yes, quite true. But such cases are far less likely than accidentally working on the same file. > A source control system can only guard against corruption or confusion > of text -- not against corruption or confusion of meaning. Hm, yeah. There is certainly no protection against mental confusion. :-) But anyhow, working on the *same* file is so exceedingly common that I would not call it confusion. Just weakness, say, or maybe oversight, or neglect, or neccessity. Whatever. Some compatibility option might turn out to be very useful. Just to enable a more "defensive" style of work. Regards, Hubert _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
