[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: Mark Phippard <markp_at_softlanding.com>
Date: 2005-11-25 21:11:46 CET

Matt England <mengland@mengland.net> wrote on 11/25/2005 03:01:33 PM:

> I find that the 'svn mv' command appears to be implemented with a "del"
> then successive "add".

Technically, it is copy followed by delete.

> Does a directory (or file) rename/move retain all of the dir/file
> prior to the move?

Yes. Because it is a copy.

> 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
> comment on this?

It is done with the same "cheap copy" effect as a copy operation. About
the only "problem" is that since it is technically a copy, when you update
a working copy it pulls down all of the new files, rather than just
performing the move in your working copy and saving time. This might come
some day.


Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.

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:16:29 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.