[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Question on client lib compatibility

From: Blair Zajac <blair_at_orcaware.com>
Date: Tue, 05 Aug 2008 12:14:01 -0700

Goetz Reyher wrote:
> Hi all,
> I've got a question concerning the backwards compatibility of newer
> versions of the SVN client libs. As documented
> per http://subversion.tigris.org/svn_1.5_releasenotes.html, the working
> copies are converted automatically to the newest versions. Say you've
> worked using a 1.4 client, and touch the local copies with a 1.5 client
> now, they get upgraded automatically (ie. without a warning). However,
> this is not true for the repositores. So one may be able to sync back to
> the older version of the repository (1.4 in the ex.) to become client
> compatible again.

I'm not sure what you're asking here. The repository and working copy upgrades
are totally unrelated to each other. If you do happen to have a 1.5.x client
touch a 1.4.x working copy and it upgrades, you can always do a checkout with a
1.4.x client or back the 1.5.x working copy down with


Even if you have a 1.5.x repository and server, the 1.4.x client can checkout
and use it.

> My question now is if you may already know if the same may occur with
> the next release of the client libs, ie. 1.6 vs. 1.5? My guess is, yes
> it could be, and we would have to take it into account. Is that the
> correct notion?

I am expecting there to be a working copy format bump in 1.6.


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-05 21:14:38 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.