Julian Foad <julianf...@btopenworld.com> writes: > I suppose I was thinking I couldn't be sure that the same path was > used in each possible case. Looking at it again, if dst_path is not a > URL then it would be reasonable to assume that all relevant changes > are on the same filesystem as dst_path. Even more so if we use the > child of dst_path instead, in the copy_as_child case; then the path > used would be, I think, the same as it was when the > sleep_for_timestamps calls were distributed among the leaf functions > before my patch.
The path is used to estimate the timestamp resolution, it dosen't matter which path in the destination is used. The other thing to consider is a move between working copies: the source might be on a filesystem with 1s sleeps while the destination is on a filesystem with 1ms sleeps. Even then it should be OK to use dst_path because the source is only getting the delete so there are no timestamps of concern on that filesystem. -- Certified & Supported Apache Subversion Downloads: http://www.wandisco.com/subversion/download
