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

Re: Compatibility Question

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2007-09-14 23:29:05 CEST

On 9/14/07, Micah Elliott <mde@micahelliott.com> wrote:
> On 2007-09-14 ANDREW.LUCAS@L-3Com.com wrote:
> > For subversion, can I mix 1.4.2 clients with a version 1.4.5 server?
> According to the Hacker's Guide:
> http://subversion.tigris.org/hacking.html#release-numbering
> "When the major number changes, all bets are off."
> So I would expect this to not be a problem from one minor release
> to the next, but for a minor release change I see a case on one
> machine where my client is too old to talk to my server.
> client$ svn --version
> svn, version 1.1.4 (r13838)
> compiled Feb 6 2006, 16:31:47
> client$ svn ls
> svn: This client is too old to work with working copy ''; please get a newer Subversion client
> server$ svn --version
> svn, version 1.4.3 (r23084)
> compiled Mar 28 2007, 22:48:32
> Granted, I didn't read the whole section, and I'm not too worried
> about it in this case, but it is somewhat surprising.


Working copy and repository formats are backward- and
forward-compatible for all patch releases in the same minor series.
They are forward-compatible for all minor releases in the same major
series; however, a minor release is allowed to make a working copy or
repository that doesn't work with previous minor releases, where
"make" could mean "upgrade" as well as "create".""""



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 14 23:25:38 2007

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.