On Fri, Dec 23, 2016 at 08:06:38AM +0100, Andreas Krey wrote:
> On Thu, 22 Dec 2016 13:48:47 +, Stefan Sperling wrote:
> > Since each .svn dir lives in a separate working copy its path is not a
> > global system setting.
>
> A safer alternative would be to look, when in /home/ak/some/wc, for
>
On Fri, 23 Dec 2016 09:30:45 +, Stefan Sperling wrote:
...
> Well, at the time the wc-ng effort was started, a centralized .svn was
> one of the design goals. That's why the DB schema is the way it is.
See, I thought, wc-ng was done, with the single .svn directory
(modulo externals). Having .s
Andreas Krey wrote on Fri, Dec 23, 2016 at 11:56:40 +0100:
> On Fri, 23 Dec 2016 09:30:45 +, Stefan Sperling wrote:
> ...
> > Well, at the time the wc-ng effort was started, a centralized .svn was
> > one of the design goals. That's why the DB schema is the way it is.
>
> See, I thought, wc-ng
Jakub Petr wrote on Thu, Dec 22, 2016 at 10:28:24 +0100:
> Why the "transmitting phase" should take so long?
Usually it's because of virus scanners intercepting the disk operations
(opening/writing files).
What makes you think the slowness is svnserve's fault? Is the commit
faster over file:// t
On Fri, Dec 23, 2016 at 11:56 AM, Andreas Krey wrote:
> On Fri, 23 Dec 2016 09:30:45 +, Stefan Sperling wrote:
> ...
>> Well, at the time the wc-ng effort was started, a centralized .svn was
>> one of the design goals. That's why the DB schema is the way it is.
>
> See, I thought, wc-ng was do
