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

Re: on-the-fly lock checking

From: Andy Whitcroft <apw_at_shadowen.org>
Date: 2004-12-03 19:24:49 CET

C. Michael Pilato wrote:
> I began a rebuttal. Then I actually applied thought. Added a pinch
> of sanity check from Ben Collins-Sussman. And the response is that
> there is no rebuttal to be had.
> I suppose we can do much of this right now. Ben can rev create_txn(),
> adding two parameters (one for on-the-fly lock checking, one for
> out-of-dateness). We can implement the on-the-fly lock checking in
> the FS. We can document that we don't do OOD checks yet, and return
> FEATURE_NOT_IMPLEMENTED if that boolean is TRUE.
> svn_repos_begin_txn_for_commit/update() can pass FALSE for OOD
> checking parameter (now and forever), and we can start deprecating
> functions.

Can we not at least use a flags mask or something ... more and more
params for each 'modifier' seems over kill.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 3 19:32:39 2004

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.