Kevin Hung wrote:
> For simplicity, let's assume that there is only one file in the project.
> So the directory inside the repository looks something like,
>
> .../svnrepos/proj/file1.txt
>
> We made a few changes to file1.txt and so file1.txt has revision 1 and 2.
>
> Now we rename the directory proj to newproj inside the repository
> browser. We also switch the working copy to point to
> .../svnrepos/newproj/file1.txt. From the log messages window of
> file1.txt, I can see all the revisions including 1 and 2. I can even
> diff between rev 1 and 2 inside the Log Messages window. This gives me
> an impression that TSVN or SVN can follow the history back to even rev 1
> and 2.
>
> However when I want to have revision 2 into my working folder (using
> Update Item To Revision), TSVN deletes the file1.txt in my working
> directory. I understand why this happens. It is because rev 2 does not
> exist in svnrepos/newproj/file1.txt.
>
> But to be consistent with other operations (eg. diff) in the Log
> Messages window, should TSVN or SVN be able to follow the history of
> file1.txt and go back to svnrepos/proj/file1.txt to get rev 2?
Subversion follows the history. But a history is always tied to the
whole repository. If you now just update a *file* to a revision where
that file didn't exist with that name but was actually in another
folder, Subversion doesn't follow the history. If you would have updated
the parent directory of the move you did to that earlier revision, the
file would have been deleted and created in the old location.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Feb 22 20:21:05 2006