[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-26 18:22:47 CET

On Sat, 2005-03-26 at 09:26, Ben Collins-Sussman wrote:
> Any program that links to libsvn_repos 1.2, and then opens a repository,
> will auto-upgrade the repository's 'format' file. This could be an svn
> 1.2 client using file:///, or it could be *any* version of mod_dav_svn
> or svnserve that just happens to link to the libsvn 1.2 libraries.

Here's an idea I don't think anyone has come up with yet:

Disable locking by default in 1.2. Turning on locking implies a format
bump. "svnadmin create" can (by default) continue to create
1.1-compatible repositories.

The exact mechanism for turning on locking could vary. It could be an
svnadmin command, or a manual edit of a repos config file (which we'd
have to introduce, it looks like). "svnadmin create" could have a flag
to create a repository with locking enabled, of course.

This idea mirrors my plan for introducing path hashing in FSFS. The
philosophy is: we can have new functionality in 1.x releases which
requires a non-backward-compatible schema change, but rather than
magically upgrading repositories to the new schema, we should require
the new functionality to be explicitly enabled. When 2.0 rolls around,
we can turn all that stuff on by default.

(I'm sure CEE would want to aggressively enable locking, but that could
be done within CEE without Subversion being so aggressive.)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Mar 26 18:54:52 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.