> From: Sukhmeet Toor [mailto:toorsukhmeet@gmail.com]
>
> Below is the output of a "svn log -v" issued at the top level of the
> working copy of my test repository (my comments are indicated with *'s
> below). Notice first that some moves are treated as a DELETE followed
> by an ADD (r9), while some are treated as an ADD followed by a DELETE
> (r4 and r8). The problem that I'm facing is that in r9, the base
> revision for newdir is 8 while it should have been 4, as it was last
> modified in revision 4 (moved from /dir). Now, my guess is that in
> this case the DELETE happened before the ADD (and not in the reverse
> order), and hence the base revision of /newdir got touched up to 8.
Any time something is copied in the repository (and I assume, when something
is moved), it is always copied from some specific revision of some specific
path. in this case:
------------------------------------------------------------------------
r9 | stoor | 2005-06-27 11:19:26 -0400 (Mon, 27 Jun 2005) | 1 line
Changed paths:
A /dir2/newdir (from /newdir:8)
D /newdir
/dir2/newdir@9 is copied from /newdir@8. Of course, /newdir@8 is the same
as /newdir@4, but Subversion doesn't record that information at that moment.
But this is what you expect if you have a WC at rev 8, do "svn mv /newdir
/dir2/newdir", and commit -- /newdir in your WC was at rev 8.
You could get the effect your are looking for my something grotty like "svn
delete /newdir ; svn copy -r4 http://.../newdir /dir2/newdir", but why do
you want to?
Dale
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 27 19:33:21 2005