Re: Semantics of Move

On 15.08.2013 17:01, Julian Foad wrote:
> Is this acceptable?

Looks OK, from a quick review.

> This means that combining the two separately
> committed changes "copy" and "move a child" into a single commit will
> result in semantic data loss, which we are trying to avoid.

Not really. The copied+moved child node will still have copyfrom
information linking it to the source of the copy. That doesn't trivially
tell us how the node came to be at the new location, but there are other
cases where that's not tracked (e.g., sequential local renames followed
by a commit; only the result will be tracked, not the intermediate
(wc-local) states).

-- Brane

-- 
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. brane_at_wandisco.com