Re: "svn commit" performance

On Tue, Jul 08, 2003 at 09:00:02PM +0100, Philip Martin wrote:
> > so what we need to do is lock the grandparent non-recursively and
> > each target recursively, also checks if all target are from the same
> > repository.
>
> What's a "grandparent", how does it relate to a target? Is it the
> common ancestor?

I menat the base_dir in svn_client_commit that is being treelocked, referred
as "grandfather directory" in the code. the treelock is what I am trying avoid.

> Hmm, it appears you only want to support a single working copy. In
> that case I would avoid the probe functions and simply use the wc
> entries to identify directories, and simply generate some error if a
> directory is obstructed or missing.
>
> How about a function like
>
> svn_error_t *
> svn_wc_adm_open_descendant (svn_wc_adm_access_t *adm_access,
> const char *descendant,
> svn_boolean_t write_lock,
> apr_pool_t *pool);

ah, this looks cleaner than what I was doing with entry url
and path checking. I'll probably svn revert my stuff.

It'd be cool if you could do this easily since I'm still getting familiar
with the api. :)

Cheers,
CLK

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 8 22:25:24 2003