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

On 11/25/05, Matt England <mengland@mengland.net> wrote:
> Hello,
>
> I find that the 'svn mv' command appears to be implemented with a "del"
> and then successive "add".

Yes. As an add-with-history to be exact.

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

Yes. That's the 'with-history' part above.

> I sure hope that it does; without it, my swdev project
> will have some further challenges.
>
> 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?

Umm, well, you didn't ask whether the 'with-history' means the change
gets sent to the client that way (ie as a rename). I guess that's
what you're asking for here.

The answer is 'no': the del+add gets transmitted just as that to the client.

> 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.

bye,

Erik.
Received on Fri Nov 25 21:19:01 2005