[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: Simon Large <slarge_at_blazepoint.co.uk>
Date: 2004-10-14 17:22:17 CEST

"Mark Phippard" wrote on 10/14/2004 10:40:07
> > *sigh*
> >
> > Maybe you guys are right. Maybe it's just too hard to try and make
> > single client cater to *both* the techie crowd ("do exactly what I
> > 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
> > TSVN folks to implement some of these helpful behaviors in the case
> > updating hijacked files. Maybe TSVN can also implement a command
> > means "update and lock" in one step.
> I think it would be a great idea to
> involve Stefan in this process, but even if we don't I am confident he
> will make TSVN handle this as gracefully as possible.

Absolutely agree. But of course it will only work on Windows. On systems
where there is no GUI available, the end user still has to use CLI, so
it still needs to be as graceful as it can be, within its limitations.


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