You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Florian Weimer <fw...@bfk.de> on 2009/10/20 07:06:51 UTC
Recording a move after the fact
"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
is to move the target someplace else, run "svn copy -r BASE TARGET",
followed by "svn remove SOURCE", and move back the original target
file. Is this correct?
--
Florian Weimer <fw...@bfk.de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2409261
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Recording a move after the fact
Posted by Ryan Schmidt <su...@ryandesign.com>.
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.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2409288
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Recording a move after the fact
Posted by Florian Weimer <fw...@bfk.de>.
* 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.
--
Florian Weimer <fw...@bfk.de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2409287
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Recording a move after the fact
Posted by Ryan Schmidt <su...@ryandesign.com>.
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?
> is to move the target someplace else, run "svn copy -r BASE TARGET",
> followed by "svn remove SOURCE", and move back the original target
> file. Is this correct?
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2409275
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].