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

Re: svn_client_move7 and mixed-revisions

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Tue, 12 Mar 2013 21:02:27 +0100

On Tue, Mar 12, 2013 at 8:44 PM, Branko Čibej <brane_at_wandisco.com> wrote:
> I have to agree with Mark. As long as we don't know how to track a
> mixed-revision move in all cases, then it's better to revert to copy+delete
> than to block the move. Ideally only for those parts of the move source that
> are actually out of date with regard to the repository, but I take it we
> haven't got that far yet.

Random thought: can move tracking be "repaired" after the fact? If
there were an API to do so, users / GUI's could repair such "broken
(legacy) moves" at some point (either automatically or at the request
of the user after he's gotten some hint by the GUI (and perhaps after
some operations such as updating, if necessary)).

Received on 2013-03-12 21:03:20 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.