On 03/13/2013 10:15 PM, Julian Foad wrote: > The interesting case here is a file replaced with an identical file: > that's the only case where it's unchanged if ignoring ancestry but > otherwise it's changed.
This may, in fact, be the only case that's interesting to our discussion. But I trust you realize that it's not mere file replacement that's affected here. Ignoring ancestry on the server side will transform directory replacements, too, converting them (editor-wise) into a normal open_directory() (perhaps with propchanges) where a full tree deletion+addition would normally have been transmitted. [Deferring further comment until we unearth the reasoning behind switch supporting --ignore-ancestry at all.] -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Enterprise Cloud Development
signature.asc
Description: OpenPGP digital signature
