No problem. That was a good tip from Ryan on the start-commit hook. I wish I had know about it, although we did publicize to our users well in advance that they needed to upgrade and they could do it anytime before we did our server upgrade. I really only got one call from a user and he was and Eclipse user.
Regards, Tom From: Alin [mailto:alin.tomoi...@ttu.edu] Sent: Thursday, June 17, 2010 4:29 PM To: Ryan Schmidt; Thomas Loy Cc: users@subversion.apache.org Subject: Re: older versions of the subversion server Ryan and Thomas, Thank you very much for your advice. -----Original Message----- From: Ryan Schmidt <subversion-20...@ryandesign.com<mailto:ryan%20schmidt%20%3csubversion-20...@ryandesign.com%3e>> To: Thomas Loy <thomas....@cbeyond.net<mailto:thomas%20loy%20%3cthomas....@cbeyond.net%3e>> Cc: Tomoiaga, Alin <alin.tomoi...@ttu.edu<mailto:%22Tomoiaga,%20alin%22%20%3calin.tomoi...@ttu.edu%3e>>, users@subversion.apache.org <users@subversion.apache.org<mailto:%22us...@subversion.apache.org%22%20%3cusers@subversion.apache.org%3e>> Subject: Re: older versions of the subversion server Date: Thu, 17 Jun 2010 15:24:56 -0500 On Jun 17, 2010, at 15:18, Thomas Loy wrote: > On the bright side, we had virtually no issues on our upgrade – the major > issue was trying to get all of our users to upgrade their clients. There is at least a way you can automate advising your users to upgrade to Subverison 1.5 or later if they have 1.4.x or earlier: the start-commit hook script. This hook script will be passed a list of client capabilities; if the client capabilities do not include mergeinfo, you know it's older than 1.5. You could at that point abort the commit and print an error message advising the user to upgrade their client. http://svnbook.red-bean.com/en/1.5/svn.ref.reposhooks.start-commit.html I don't know of a way to detect the client version beyond that, though. And unfortunately early versions of 1.5.x weren't totally satisfactory for merge tracking, so you really do want your clients to be the latest version.
