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

Re: Dir/file renames: trying to retain history & save capacity

From: Duncan Murdoch <subversion_at_murdoch-sutherland.com>
Date: 2005-11-25 21:09:44 CET

On 11/25/2005 3:01 PM, Matt England wrote:
> Hello,
> I find that the 'svn mv' command appears to be implemented with a "del" and
> then successive "add".
> Regardless:
> Does a directory (or file) rename/move retain all of the dir/file history
> prior to the move? I sure hope that it does; without it, my swdev project
> will have some further challenges.

Yes, it maintains the history. This is a basic feature of Subversion,
one way in which it improves on CVS.
> I also need to change the name of a directory in my repo that has an
> enormous amount of capacity underneath it. If 'svn mv' truly
> deletes-then-adds, this will take a substantial amount of bandwidth (for
> remote access), capacity, time...all things I'd like to save. Can anyone
> comment on this?

That doesn't copy any data, it just creates new nodes with the new names
and marks the old names as not in use any more. The amount of work is
proportional to the number of files moved (because each has to maintain
its history), but not to the amount of data in them.

> Is there an alternative to 'svn mv' for file/dir renames/repositioning
> (without a directory layout)?
> I'm sure this is a faq; I'd be happy to go read the answer if someone can
> point me in the right direction.

I don't think it is, but it probably should be. If you read the book
and use Subversion for a while you'll just know the answer, but if you
want a single place to look it up, I don't know if there is one.

Duncan Murdoch

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 25 21:13:58 2005

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

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