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

2013-02-19 Thread Ben Reser
On Mon, Feb 18, 2013 at 7:18 PM, Justin Erenkrantz wrote: > +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 +1

Re: svn commit: r1447487 - /subversion/trunk/subversion/svn/svn.c

2013-02-19 Thread Johan Corveleyn
sion.apache.org >> Subject: Re: svn commit: r1447487 - /subversion/trunk/subversion/svn/svn.c >> >> "Bert Huijben" writes: >> >> >> + This blocks every other application from accessing our wc.db at > the >> same >> >> + time as

RE: svn commit: r1447487 - /subversion/trunk/subversion/svn/svn.c

2013-02-19 Thread Bert Huijben
> -Original Message- > From: MARTIN PHILIP [mailto:codematt...@ntlworld.com] On Behalf Of > Philip Martin > Sent: dinsdag 19 februari 2013 11:50 > To: Bert Huijben > Cc: dev@subversion.apache.org > Subject: Re: svn commit: r1447487 - /subversion/trunk/subversion

Re: svn commit: r1447487 - /subversion/trunk/subversion/svn/svn.c

2013-02-19 Thread Branko Čibej
On 19.02.2013 11:49, Philip Martin wrote: > Users that mix the command line with GUIs can switch off exclusive > locking. If we switch the default then users that want performance > need to switch on exclusive locking. I don't know which group is > bigger, users who want performance or users who wa

Re: svn commit: r1447487 - /subversion/trunk/subversion/svn/svn.c

2013-02-19 Thread Philip Martin
"Bert Huijben" writes: >> + This blocks every other application from accessing our wc.db at the >> same >> + time as this process. So instead of using the working copy lock >> functions >> + as designed other processes will already block before being able to >> check >> + that

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

2013-02-19 Thread Daniel Shahaf
Justin Erenkrantz wrote on Mon, Feb 18, 2013 at 22:18:33 -0500: > +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 +1

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

2013-02-18 Thread Justin Erenkrantz
On Feb 18, 2013 7:08 PM, "Stefan Sperling" 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

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

2013-02-18 Thread Stefan Sperling
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. > > An

RE: svn commit: r1447487 - /subversion/trunk/subversion/svn/svn.c

2013-02-18 Thread Bert Huijben
> -Original Message- > From: rhuij...@apache.org [mailto:rhuij...@apache.org] > Sent: maandag 18 februari 2013 21:51 > To: comm...@subversion.apache.org > Subject: svn commit: r1447487 - /subversion/trunk/subversion/svn/svn.c > > Author: rhuijben > Date: Mon Fe