Updating svn server
Subversion clients is were much of the grunt work is handled, and most versions of the Subversion clients can work with almost any version of the server.The last release where the server version really made a difference to the client was the change from release 1.4 to release 1.5 when merge tracking was added.
However, this may not be as big a problem as you may think.This allows you to update your working copy to a specific revision, not only to the most recent one.Suppose your working copy is at revision 100, but you want it to reflect the state which it had in revision 50 - then simply update to revision 50. This opens a new dialog where you can check all items you want in your working copy and uncheck all the items you don't want.If the file you are updating has changed name, you may even find that the file just disappears from your working copy because no file of that name existed in the earlier revision.You should also note that the item will show a normal green overlay, so it is indistinguishable from files which are up-to-date.You can also choose whether to ignore any external projects in the update (i.e.
projects referenced using error messages when you try to commit them!
can occasionally be useful to see what your project looked like at some earlier point in its history.
But in general, updating individual files to an earlier revision is not a good idea as it leaves your working copy in an inconsistent state.
Merge tracking had been greatly improved in version 1.6, but that doesn't really affect the interactions between the client and server.
Let's take the latest changes in Subversion 1.8: Of all the features, only one depends upon the version of the server being 1.5 or greater (and 1.4 has been obsolete for quite a while.
I then go to website directory on the linux box where I want to update these changes from the repository to the directory there.