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

Re: svn commit: r26495 - in trunk: subversion/libsvn_client subversion/tests/cmdline www/merge-tracking

From: Daniel Rall <dlr_at_finemaltcoding.com>
Date: 2007-09-10 09:50:10 CEST

On Sep 8, 2007, at 4:50 PM, David Glasser wrote:

> On 9/7/07, dlr@tigris.org <dlr@tigris.org> wrote:
>> Author: dlr
>> Date: Fri Sep 7 12:03:21 2007
>> New Revision: 26495
>>
>> Log:
>> Complete issue #2822, handling propagation of mergeinfo for WC -> WC
>> copy/move operations.
>>
>> This commit makes WC -> WC copy/move operations, in conjunction with
>> the --use-merge-history option, now require repository access
>> (e.g. users may need to be online to use 'svn cp -g wcpath1 wcpath2'
>> with a remote repository). Such copy/move operations which do not
>> use
>> the --use-merge-history flag won't properly propagate inherited or
>> implied mergeinfo to the destination.
>
> As a user, when would I want to use "svn cp -g" and when just
> standard "svn cp"?
>
> (Is it 'I use always use "svn cp -g" unless I'm on a plane'?)

Yes, you'll always want 'svn cp -g'.

I'd prefer to avoid having to contact the repository at all, but the
client simply doesn't have sufficient information. We've discussed
the possibility of delaying contacting the repository until a
subsequent 'svn merge' or 'svn update' or 'svn commit' or some such
occurs, but work on such a solution hasn't been scoped.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 10 09:39:55 2007

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