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

exclusive WC locks by default? (was: Re: svn commit: r1447487 - /subversion/trunk/subversion/svn/svn.c)

From: Stefan Sperling <stsp_at_elego.de>
Date: Tue, 19 Feb 2013 01:07:35 +0100

On Mon, Feb 18, 2013 at 10:21:16PM +0100, Bert Huijben wrote:
> If I would use 1.8 to run
>
> svn diff |more
>
> And leave that open in a console I would block TortoiseSVN, AnkhSVN, Subclipse, etc on my entire working copy, while this command doesn't even obtain a working copy lock.
>
> And as a developer on both 'svn' and AnkhSVN I often use 'svn diff' just for reviews.
>
> And all those other clients would just hang without a way to recover...

I only use the command line but run 'svn' commands concurrently quite often.

E.g. I run 'svn diff' while 'svn commit' has the log message editor open.
I also use 'svn log --diff' a lot and sometimes still have it running while
committing from the same working copy.

I've disabled exclusive locking in my client configuration for this reason
and wouldn't mind either if exclusive locking was off by default.
Received on 2013-02-19 01:08:12 CET

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.