RE: Progress on SHA-1 fixes in patch releases?

The server side fixes currently need a third vote for backporting. These fixes are nominated for 1.8.x and 1.9.x.

I don’t think we can really do much more on the released versions without a backwards incompatible change to the working copy… And I’m still not convinced that we should really change the WC code just to support using Subversion to explicitly store collisions.

On trunk there are even more problems, as Ivan committed a change that made us rely on sha-1 even more than before to check for local changes. I already pinged that thread a few times, but there is no progress there.

If no progress is reported on the discussed points I would like to see that change to notice differences (at least temporarily) reverted.

     Bert

Sent from Mail for Windows 10

From: Stefan Sperling
Sent: donderdag 30 maart 2017 13:23
To: Paul Hammant
Cc: Subversion Development
Subject: Re: Progress on SHA-1 fixes in patch releases?

On Thu, Mar 30, 2017 at 06:30:55AM -0400, Paul Hammant wrote:
> My apologies. When I wrote "No patch releases though, right?" my intention
> was to communicate "No patch releases YET though, right?

There are no patch releases yet, no.
Received on 2017-03-30 19:04:37 CEST