On Fri, Jun 27, 2003 at 10:40:43PM -0500, cmpilato@collab.net wrote:
> Ross Mark <rossm@controllingedge.com.au> writes:
>
> > I hit the exact same problem. I installed the 0.24.2 client on a new
> > box and could not check out anything from my server which was
> > 0.20.0. Upgrading the server to 0.24.2 fixed the problem. The 0.23
> > clients worked happily against the old version. It is also weird that
> > with the 0.24.2 client that there were no error message just an empty
> > working directory (with the .svn dir).
> >
> > I had been avoiding upgrading the server due to possible down time and
> > given we were in the middle of a major product release unnecessary
> > changes did not seem like a good idea.
>
> Pre-1.0, our stated compatibility promise is that a server and client
> that are no younger than one minor revision apart will work together.
>
> So, a 0.24 client will work with a 0.23, 0.24, or 0.25 server. A 0.20
> server will work with a 0.19, 0.20, or 0.21 client. Outside that, all
> bets are off. Once we approach 1.0 though, we won't be expecting
> everyone to keep up with bleeding edge like this any more.
OK, thanks for the info. I'll look to see how soon I can upgrade the
subversion binary on the remote machine.
Subversion has been working wonderfully for my needs so far, so my thanks
go to all the developers. It's nice to see now that the Linux Kernel is
accessible too, and I've downloaded the 2.4 tree just to see subversion
in action on such a large repository. Needless to say it has handled the
2.4 kernel tree without difficulty. Nice.
Art Haas
--
Man once surrendering his reason, has no remaining guard against absurdities
the most monstrous, and like a ship without rudder, is the sport of every wind.
-Thomas Jefferson to James Smith, 1822
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jun 28 06:05:30 2003