On Feb 18, 2013 7:08 PM, "Stefan Sperling" <s...@elego.de> wrote: > > 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.
+1 - "svn diff" while running "svn commit" (blocking waiting for $EDITOR to exit) is my SOP as well. If we break that by default, I consider it a regression. -- justin
