Julian Foad writes:
> The root of the problem, as I recall, is the WC DB requirement that,
> before updating the DB entry for directory "DIR" to revision REV,
> there must be child entries in the DB corresponding to (at least) all
> the children of DIR@REV in the repository. I'm not 100% sure ab
Philip Martin wrote:
> Julian Foad writes:
>> Philip Martin wrote:
>>> [Conceivably
>>> the RA implementation of the current Ev2 API could deltify the list
>>> sent back by caching the list received but that's horrible and doesn't
>>> solve the problem of getting the list in the first place.]
>>
Julian Foad writes:
> Philip Martin wrote:
>> [Conceivably
>> the RA implementation of the current Ev2 API could deltify the list sent
>> back by caching the list received but that's horrible and doesn't solve
>> the problem of getting the list in the first place.]
> Why is this different from
Philip Martin wrote:
> Another problem with Ev2. Consider a cheap copy:
>
> svn cp ^/trunk ^/branches/foo
>
> With Ev1 this commit sends only a small amount of data across the wire.
> This is true even as the number of branches gets large. In the past
> there was a backend "big directory" s
Another problem with Ev2. Consider a cheap copy:
svn cp ^/trunk ^/branches/foo
With Ev1 this commit sends only a small amount of data across the wire.
This is true even as the number of branches gets large. In the past
there was a backend "big directory" storage problem, but that was solved
5 matches
Mail list logo
