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

Re: locking a file renders repos unusable with older clients

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2005-03-30 18:38:30 CEST

On Wed, 2005-03-30 at 10:19, C. Michael Pilato wrote:
> It was suggested previously that we simply auto-upgrade the repository
> without bumping the format number. The result, of course, is that 1.2
> and 1.1 clients can work on a pre-1.2-turned-1.2 repository without
> any "yer client cain't support this 'positurry" errors. But as the
> foremost goal of the locking functionality is the prevention of wasted
> time, I cannot support this idea either. I'd be pretty upset if I
> locked a binary file to make a slew of edits and someone else came
> along and committed atop it anyway (making me out of date) simply
> because their client didn't know any better.

That could only happen for an environment using ra_local. An
environment using either kind of server would still have locks enforced.

I tend to believe that the intersection of environments using ra_local
and enviroments using locks will be vanishingly small.

> I am currently compelled (by reasons of having some semblance of
> sanity as a personal goal) to bail on this task, and further to
> suggest that we stick with the auto-upgrade mechanism as-is.

Don't all of the repository sanity issues apply just as much to
auto-upgrade as they do to manual upgrade?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 30 18:40:11 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.