This is the mail archive of the
mailing list for the Cygwin project.
Re: Rolling back to 1.6.x Subversion
On 11/17/2011 10:09, Jon Clugston wrote:
> On Thu, Nov 17, 2011 at 10:37 AM, Jeremy Bopp <firstname.lastname@example.org> wrote:
>> I want to think that they only change the working copy format when the
>> minor version changes, but I also think that they have done that with
>> every minor version transition since at least 1.4. I know I remember
>> seeing the client request to upgrade my working copies at least once
>> before anyway. Whether or not that upgrade was required, I can't say.
> This is all explained quite clearly in the documentation on the
> Subversion web site. Each minor release is allowed to change the
> working copy format in a non-compatible way (the lower numbered
> clients can't safely use it). This simplifies the development of
> Subversion but causes a (to me at least) very minor annoyance that all
> clients that will use the same working copy must be at the same minor
> release. This, however, doesn't stop anyone else who writes
> Subversion clients from transparently supporting multiple client
> versions simultaneously (and dealing with the complexity that
Thank you for confirming my memory regarding these format changes.
Still, while it makes sense for the project to make backward
incompatible changes at times, it still seems odd that the new clients
wouldn't support using the working copies from at least 1 minor version
back in order to ease interoperability between SVN client implementations.
I could see that the new clients wouldn't *create* older version working
copies in order to encourage adoption of the changes, but it wouldn't
seem too hard on the face of it to keep around a compatibility layer
from the last minor version in order to *use* an older working copy.
It's the maintainers' decision how they build their project, of course.
I just find this aspect surprising.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple