Hi, Stephen Connolly wrote: > I remember reading before about a hack/trick that allows you > to ensure that the client is at least mergeinfo aware when the > repository is served via Apache httpd.
You can have a start-commit hook. It can reject commits from clients that don't have the "mergeinfo" capability. http://svnbook.red-bean.com/en/1.5/svn.ref.reposhooks.start-commit.html > A better trick would allow blocking clients less than 1.6.13 from connecting ;-) Subversion sends it's version in the User-Agent string. You can test that in your Apache config file. (But this is probably a bad idea unless it's an internal SVN server that's locked down by corporate policy). http://httpd.apache.org/docs/2.2/howto/access.html#env Bear in mind that some people may not be using the official Subversion client. Kind regards, Jon ********************************************************************** This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Cabot Communications Ltd. If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Cabot Communications Limited Verona House, Filwood Road, Bristol BS16 3RY, UK +44 (0) 1179584232 Co. Registered in England number 02817269 Please contact the sender if you believe you have received this email in error. ********************************************************************** ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
