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

Re: Locking UI comments

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2004-10-13 18:14:56 CEST

Ben Collins-Sussman <sussman@collab.net> writes:

> I was describing what might happen in a world where 'lock' and
> 'update' are separate actions, and have no mutual requirement or
> dependence at all. My fear is that in such a world, users forget to
> 'update' before locking, so that they end up locking an out-of-date
> file.
> But your recommendation above fixes that.

Thinking a bit more, if you had suggested the locking command be

   $ svn update --lock foo.c

rather than

   $ svn lock foo.c

I think I would have accepted it without a question. Appearances are
everything! I guess that means I don't really object to "svn lock"
running update.

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 13 18:31:02 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.