[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: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-10-14 16:10:36 CEST

"Sander Striker" <striker@apache.org> wrote on 10/14/2004 10:03:15 AM:

> I think the "huh?" arises much earlier: it starts with firing up
> a shell. Or, when they end up in vi when they commit ;)
> [ # calls administrator: "How do I get out of this thing?!" ]
> Seriously, the user group you are now standing up for is much more
> likely to use a GUI than to use the cmdline client. I'd like to see
> us try to keep the cmdline client consistent and would propose that
> we generate a 'regular' conflict. GUIs can solve this issue in their
> own way (the API should allow for detecting if a conflict was
> generated because of a hijacked lock).

I wanted to say something like this too. TSVN handles this fairly easily.


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 14 16:10:51 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.