Re: Moving a moved file

You're right -- the problem here is implementation. I suppose we
*could* simply not care about the inconsistent ancestor problem, and
implement transitivity anyway. In other words, 'svn cp A B' would make
a special check -- if A is schedule-add-with-history, then make B use
the same ancestor-URL. That means that there would be absolutely no
difference between

svn cp A B
svn cp A C
svn commit

  and

svn cp A B
svn cp B C
svn commit

In both cases, B and C will claim to be direct descendants of A. Is
that really okay? In the second scenario, is it really okay that B and
C are siblings, rather than ancestor/descendant relationship? Doesn't
that bother you?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 26 20:11:41 2003