All true, but it would still have been nice for André's use case to
work. 'svn log' needs almost zero information from the wc, after all...
Stefan Sperling wrote on Sun, Feb 19, 2012 at 13:32:46 +0100:
> On Sun, Feb 19, 2012 at 03:25:52AM +0100, André Hänsel wrote:
> > Hi list,
> >
> > recently I noticed that I cannot view the log while an update of a working
> > copy is running. It's quite annoying. I wonder if it has always been this
> > way or if this is new in 1.7.
>
> This is new in 1.7. It happens because it uses sqlite for storage.
> While the sqlite DB is open for writing, readers are blocked.
> See http://sqlite.org/lockingv3.html
>
> > Isn't "svn log" a completely remote operation without involving the local working copy?
>
> Only if you pass a URL as argument. If you pass a local path, or
> a shortcut URL like ^/trunk, 'svn log' needs to read meta-data to
> figure out the URL to use.
Received on 2012-02-19 19:31:34 CET