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

Re: Rejecting commits to a 1.5 server from clients < 1.5

From: Blair Zajac <blair_at_orcaware.com>
Date: 2007-10-26 16:29:47 CEST

Jack Repenning wrote:
> On Oct 26, 2007, at 5:17 PM, Miha Vitorovic wrote:
>> IMO, it's not about contradiction, it's about giving the users a choice.
>> They can mix the clients, or the server admins can choose to force the
>> version. More choice ==> a good thing.
> Do server admins get this choice? That would be better, I agree -- and
> that was the way the conceptual proposal was originally put. But I
> think the implementation proposal that eventually developed does not
> involve choice: all 1.5 repositories will always reject all access from
> pre-1.5 clients.
> Did I miss something there?

My idea was that the repository would pass an additional argument to the
start-commit script, $OPTIONS, which would be a semicolon separated list of
client capabilities. The start-commit script could decide to reject the commit
if it didn't find the required capability.

By default, there is no start-commit script in a repository, so it would allow
all commits from any Subversion client.


Blair Zajac, Ph.D.
CTO, OrcaWare Technologies
Subversion training, consulting and support
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 26 16:30:07 2007

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.