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

Re: moving files in a smarter way

From: Ed Price <ed.price_at_gmail.com>
Date: 2006-10-11 19:21:46 CEST

> > If i move versioned files on one machine from one directory to another
> > and commit, everything works fine...
> > Now on another machine, when i do an update, the files are fetched again
> > from the server. Why isn't svn smart enough to know that these files
> > already exist on that machine in a different location, and just move
> > them locally to the new location without actually fetching them again
> > from server?
>
> Because a move is - currently - modelled as a Delete + Add, which is
> what the new client is receiving. Because of the Add, it also needs
> the new content.

I don't entirely buy that explanation, because it's not just an add,
it's a *copy*, and the WC already contains the "copyfrom" source
(or whatever it's called). [*]

I don't think it should be necessary for the holy grail of
"true renames" to be obtained before a simple copy can
be implemented efficiently.

Resolving this issue would be very nice for people who
work with large files (and/or slow/glitchy networks).

(I experience the inefficiency all the time, using svn
to store photos and videos, which I frequently move
and rename.)

-Ed

PS [*] ok ok maybe if the delete gets run first that spoils it,
but still I'd hope that could be addressed without requiring
"true rename" support.

On 10/10/06, Erik Huelsmann <ehuels@gmail.com> wrote:
> On 10/10/06, hilz <hs_74@hotmail.com> wrote:
> > Hi,
> > I asked this question on the tortoisesvn list but it seems is it a svn
> > issue, so i will ask again here.
> >
> > If i move versioned files on one machine from one directory to another
> > and commit, everything works fine...
> > Now on another machine, when i do an update, the files are fetched again
> > from the server. Why isn't svn smart enough to know that these files
> > already exist on that machine in a different location, and just move
> > them locally to the new location without actually fetching them again
> > from server?
>
> Because a move is - currently - modelled as a Delete + Add, which is
> what the new client is receiving. Because of the Add, it also needs
> the new content.
>
> This is currently being worked on ('Implement true renames'), but it's
> a multi-stage project which needs a lot of work before effects can be
> seen on the client side.
>
> HTH,
>
> Erik.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 11 19:22:52 2006

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.