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

Re: renaming in v1.8.x

From: Ryan Hathaway <rghathaway_at_starkcountyohio.gov>
Date: Fri, 02 May 2014 15:29:42 -0400

I'm no expert with Tortoise/Subversion, but I think it also somehow attaches an old history information link to the new filename upon rename's move/delete action, so that prior changes applied to the old file are still linked to the new file's change history. If you manually delete/add instead of svn_rename, this history starts over for the new file at the moment of its first commit just like any other new file.

Thank you,


Ryan Hathaway
Programmer Analyst

Office of Alan Harold, Auditor
Stark County Ohio
110 Central Plaza S
Canton, OH 44702


***Please note: My email address has changed to rghathaway_at_starkcountyohio.gov ***
>>> Andy Levy <andy.levy_at_gmail.com> 05/02/14 2:15 PM >>>
On Fri, May 2, 2014 at 2:43 PM, Rob Conde <rob.conde_at_ai-solutions.com> wrote:
> Apologize if this is a double post but the post I entered through the web interface appears to have disappeared.
> I wanted to try out the new move functionality available in svn 1.8, so I created a local repository and tried it out. I was surprised to see the rename still was modeled as a copy/delete. Am I missing something?

Are you referring to this functionality:
http://subversion.apache.org/docs/release-notes/1.8.html#moves ?

If so, as I read it moves are still a copy + delete. The change is
that the WC marks the action as a move, and won't let you commit half
of the action (the copy or the move), as previous versions did. It's
better uncommitted move *tracking* in the WC but the implementation of
the move itself is the same.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-05-02 21:30:23 CEST

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

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