Philip Martin writes:
> svnsync has a simple algorithm that writes every revprop for each
> revision.
If we put the write optimisation into svnsync, not writing unchanged
revprops, this would probably give most of the efficiency gain for the
case where the bulk of the revprops are unchanged. I
On Fri, Jul 24, 2015 at 8:58 PM, Philip Martin
wrote:
> I was thinking that perhaps we ought to provide a more accessible way to
> do this. First, modify the FS implementations to detect when a change
> is a noop that doesn't modify a value and skip all the writing.
Done in r1692650.
-- Stefa
On Sat, Jul 25, 2015 at 8:49 AM, Philip Martin
wrote:
> Philip Martin writes:
>
> > svnsync has a simple algorithm that writes every revprop for each
> > revision.
>
> If we put the write optimisation into svnsync, not writing unchanged
> revprops, this would probably give most of the efficiency
3 matches
Mail list logo