Re: locking a file renders repos unusable with older clients

> I am tempted think in most cases where network admins are involved
> subversion runs on apache or svnserve. On these systems you need to
> upgrade the server and then the repository manually to enable locking.
> No auto-update here. So 9,500 of the 10,000 admins need to do some
> manual work anyway.

I do not think this is true. I believe the repository will auto-update
regardless of the RA method used to access it.

Perhaps we should explore ghudson's ideas more. Why do we really need to
bump the version number? It seems like the only point is to prevent non
1.2 clients from ignoring locks. I am not sure this is such an important
point since we would only be talking about file:// access. Presumably the
svn or Apache servers are capable of enforcing locks against any client?

I am not sure that people that are using file:// access exclusively would
be that concerned about this "hole", and would probably prefer it over the
current scenario.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Mar 26 14:07:29 2005