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

can mod_dav_svn 1.5 deny access from earlier clients?

From: David Moxon <dmoxon_at_gmail.com>
Date: Mon, 28 Jul 2008 11:49:34 -0700

I manage a large subversion repository, and I am interested in upgrading to
1.5. However, it will not be possible for me to upgrade all our user's svn
clients at the same time, since they are managed indvidually by the users

My concern is this:
1. We begin using subversion 1.5's merge tracking feature throughout the
2. A user with an older subversion client does some (legacy-style) merge
operations on the repository.
3. The svn:mergeinfo on the server is then incomplete/corrupt?

I tried to look for how subversion 1.5 handles this mixed client server
version situation, but it is unclear. The documentation states that merge
tracking is only supported if both server and client are version 1.5, but
does not state what happens if an earlier client attempts to perform
(legacy-style) merges against a 1.5 server and repository with merge
tracking information in use by others.

If this scenario is not supported, is it possible to deny access to a
repository from clients earlier than 1.5?


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-28 20:50:04 CEST

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.