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

Re: Problem : svn: working copy locked:

From: Peter Davis <peter_at_pdavis.cx>
Date: 2003-01-09 20:25:28 CET

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Do working copies work over NFS? Other than that edge-case, wouldn't it be
at least possible to test that the process that created the lock is still
running, and if not, warn the user and, if running the command line client
and there is no --non-interactive, prompt the user to clear the lock?

Oh well, no matter what it would hardly save any more time and would only
be slightly more convenient (after all, that's what the up-arrow is for on
my shell). I preemptively agree that this would be too complicated and
have too much risk to be worth it.

On Thursday 09 January 2003 10:52, Garrett Rooney wrote:
> we locked the working
> copy for a reason, and just because you ran into a lock that this
> instance of svn didn't put there doesn't mean it isn't a valid lock
> (some other svn client might be locking that directory). i was under
> the impression that svn cleanup just breaks the locks and runs any
> existing logs, whihc doesn't seem to be the right thing to do if we
> don't 'know' that the locks are indeed invalid. unfortunately, we can't
> know that they are invalid, only the user can.

- --
Peter Davis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+HcyrhDAgUT1yirARAhKCAJ9tKBkZXoxKGVCRsi+15HH7qEdymQCfbiLb
ft/ei7g6QffnU2OYdMVe8pI=
=h1Wg
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 9 20:29:01 2003

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