[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Locking consensus(es) so far

From: Branko Čibej <brane_at_xbc.nu>
Date: 2004-10-18 14:17:18 CEST

Ben Collins-Sussman wrote:

> Because we're trying to keep version control *simple* for non-techies,

Now that's a new one. I disagree that Subversion's mission is to make
version control simple for non-techies.

> by avoiding the usual conflict procedure in the case of a hijacked
> file. This is all explained in section I of the locking-ui.txt
> document. I can't tell if you've read that section or not. If you
> disagree with this incentive, then we have much to discuss. :-)


You solve the non-techie problem simply by requiring locks on all files
in the repository by default, which means that a hijack can't happen
because the potential perpetrator won't be able to commit an unlocked
file (without breaking the lock, which you don't let non-techies do

-- Brane

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 18 14:17:45 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.