On 9/12/06, Thomas Harold <tgh@tgharold.com> wrote:
> David Anderson wrote:
> > * Sean Kelley <sean.sweng@gmail.com> [2006-09-12 00:07:22]:
> >>> * Due to various improvements made to the working copy library, the
> >>> working copy format has changed. Using Subversion 1.4.0 on any
> >>> working copy created by previous versions of Subversion will
> >>> SILENTLY upgrade your working copy, which means that previous
> >>> versions of Subversion will no longer be able to read it.
> >> Does this change imply that if you are using a third party client like
> >> SmartSVN, you need to wait on updating the server until all clients,
> >> such as SmartSVN, have been updated to support SVN 1.4?
> >
> > No. Any 1.X client will continue to work with any 1.Y server (though
> > features may be lost, obviously). It means that when SmartSVN starts
> > using 1.4 libraries, your working copies will be unreadable by
> > previous versions of SmartSVN.
> >
>
> Is this true even after a dump/reload to take advantage of the new diff
> format in the repository? (Or did I just misread this as being an issue
> where the new diff repository format requires 1.4 clients.)
A dump/load is entirely a server side change, it has zero effect on
clients (unless they're talking to the repository via file:/// urls),
the incompatibility he's talking about is because all Subversion 1.4
clients use a new working copy, and the JavaSVN libraries used by
SmartSVN haven't yet been updated to use it because they're a third
party product that isn't maintained by the subversion team.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 12 16:57:12 2006