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

Re: Subversion produces inconsistent base revisions for move operations

From: Sukhmeet Toor <toorsukhmeet_at_gmail.com>
Date: 2005-06-27 20:15:05 CEST

Hi Philip

Thanks for your response. Look at r4 below; If base revision was taken
as the working copy (WC) revision when the move operation was
performed, then /newdir@4 should have been copied from /dir@3 (the WC
was @3) and not from /dir@1 as the log indicates.

------------------------------------------------------------------------
r4 | stoor | 2005-06-27 12:16:05 -0400 (Mon, 27 Jun 2005) | 1 line
Changed paths:
  D /a.txt
  D /dir
  A /newdir (from /dir:1)
  A /newdir/b.txt (from /dir/b.txt:3)
  A /newdir/c.txt (from /dir/c.txt:3)

------------------------------------------------------------------------

Any thoughts?

Thanks,
Sukhmeet

On 6/27/05, Philip Martin <philip@codematters.co.uk> wrote:
> Sukhmeet Toor <toorsukhmeet@gmail.com> writes:
>
> > 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 order of the names in the log message does not imply that one
> happens before the other. As far as log is concerned they happen
> togther.
>
> > 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).
>
> Ever revision number applies to all items in the repository. newdir
> might be unchanged between r4 and r8, but that doesn't change the fact
> that you copied newdir from the r8 tree.
>
> --
> Philip Martin
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 27 20:16:06 2005

This is an archived mail posted to the Subversion Dev mailing list.

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