On Wed, Sep 17, 2008 at 8:52 AM, <gstein_at_tigris.org> wrote:
[snip]
> +/**
> + * In most cases, svn operations will deal with multiple targets. Each
> + * target may have a different administrative database, and others will
> + * be sharing a database. This function will open all relevant databases
> + * for the paths identified in @a paths. The databases will be returned
> + * in @a dbs, as a hash mapping the path to an svn_wc__db_t * value.
> + * Database handles will be shared if two paths imply the same database.
> + *
> + * The @a config will be used to identify how to locate the database
> + * for each target listed in @a paths.
> + *
> + * Results will be alloated in @a result_pool, and temporary allocations
> + * will be made in @a scratch_pool.
> + */
> +svn_error_t *
> +svn_wc__db_open_many(apr_hash_t **dbs,
> + const apr_array_header_t *paths,
> + svn_config_t *config,
> + apr_pool_t *result_pool,
> + apr_pool_t *scratch_pool);
Just trying to understand the motivation for such a function... is
this to support externals? Or is there something else that I'm
missing?
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-17 16:05:18 CEST