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

Re: Recording a move after the fact

From: Ryan Schmidt <subversion-2009b_at_ryandesign.com>
Date: Tue, 20 Oct 2009 03:55:29 -0500

On Oct 20, 2009, at 03:52, Florian Weimer wrote:

> * Ryan Schmidt:
>> On Oct 20, 2009, at 02:06, Florian Weimer wrote:
>>> "svn move" requires that the source exists, "svn copy" requires that
>>> the target does not exist. "svn add" does not allow specification
>>> of
>>> history information. So it seems the only way to achieve what I
>>> want
>> What is it exactly that you want? :) What is the situation?
> Refactoring in an IDE moves files around, updating them
> simultaneously. I want to reflect this in the working copy,
> eventually preserving history across those renaming operations.

As you know, you must use "svn mv" commands to move versioned items.
Ideally, use a Subversion-aware IDE that does this for you. If that's
not possible, then after you refactor in your Subversion-unaware IDE,
you'll have to un-refactor it on the command line (using e.g. "mv"
commands (not "svn mv" commands) to move things back the way they
were), then re-refactor using "svn mv" commands. Then you can "svn
commit" the changes.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-20 10:56:39 CEST

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