[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: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2004-10-14 16:40:07 CEST

On Oct 14, 2004, at 10:10 AM, Mark Phippard wrote:
>
> I wanted to say something like this too. TSVN handles this fairly
> easily.
>

*sigh*

Maybe you guys are right. Maybe it's just too hard to try and make a
single client cater to *both* the techie crowd ("do exactly what I say,
be predictable") and the non-techie crowd being forced to use VC
("protect me from complex VC concepts, try to help me out of messes
with interactions/suggestions").

Sander's probably right: the non-techie crowd is mostly likely using a
GUI, and most likely that's TortoiseSVN. Perhaps we can persuade the
TSVN folks to implement some of these helpful behaviors in the case of
updating hijacked files. Maybe TSVN can also implement a command that
means "update and lock" in one step.

---------------------------------------------------------------------
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:41:37 2004

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