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

Re: svn commit: r927211 - /subversion/trunk/subversion/libsvn_wc/wc_db.c

From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: Thu, 25 Mar 2010 07:42:33 -0400

On Mar 25, 2010, at 7:06 AM, Philip Martin wrote:

> Julian Foad <julian.foad_at_wandisco.com> writes:
>
>> But that would obscure the reason for it and "int levels_to_lock" is the
>> API idiom throughout Subversion.
>
> OK. I've just noticed that every caller of svn_wc__db_wclock_set
> passes zero for levels_to_lock, perhaps it doesn't need to be a
> parameter at all.

This is here strictly for backward compat. The access batons still have the notion of 'levels to lock' and we need to ensure that they still function correctly, even in the new world. 'levels to lock' should not be exposed through the wc-ng APIs at all: users either get to lock the entire tree (rooted at some subdir, of course), or none.

-Hyrum
Received on 2010-03-25 12:44:34 CET

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