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

Re: svn commit: r22414 - in branches/multiple-moves/subversion: include libsvn_client

From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: 2006-11-30 22:04:48 CET

David Glasser wrote:
> On 11/23/06, hwright@tigris.org <hwright@tigris.org> wrote:
>
>> +svn_error_t *
>> +svn_client_copy_into(svn_commit_info_t **commit_info_p,
>> + const apr_array_header_t *src_paths,
>> + const svn_opt_revision_t *src_revision,
>> + const char *dst_dir,
>> + svn_client_ctx_t *ctx,
>> + apr_pool_t *pool);
>
> Hmm. Would it be reasonable to allow you to specify different src
> revisions for different paths? (The 'svn' syntax would presumably be
> the pseudo-pegrev syntax like in "svn diff": svn cp
> svn://some/file_at_123 svn://some/other/file_at_456 svn://some/directory.)
> Or would this not have any real use cases?

I don't think we currently support pegrev syntax for single copies (see
issue 2546). We should probably implement that before worry about the
multiple version. They could be implemented together without too much
trouble.

As for use cases, I suppose if one wanted to cherry-pick specific files
at specific revisions, it would be useful to support this syntax. For
example:
svn cp svn://some/file_at_123 svn://some/file_at_456 svn://some/snapshot/dir

Kind of a "multiple retro tag" operation.

-Hyrum

Received on Thu Nov 30 22:05:14 2006

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