Hi, A while ago, I had added two move-related functions that were intended to given devs *some* backend functionality that would allow to experiment with move tracking on the client side.
I like to remove them from the 1.9 release now because the move tracking ideas that have become more substantiated recently seem to point into a different direction. The two APIs are being tracked by the following issues: * Issue #4499 "Remove move detection heuristics from public API" http://subversion.tigris.org/issues/show_bug.cgi?id=4499 * Issue #4501 "Remove svn_fs_move() API" http://subversion.tigris.org/issues/show_bug.cgi?id=4501 I think that the first one is a nice idea for how a backward- compat log improvement could look like, UI-wise in particular. Maybe, that idea can be reused at some point in the future. While the second one is theoretically independent, but it is linked to the first via the new svn_fs_path_change_* values. Moreover, we know that we will probably implement something much different for move tracking such that there is no point in releasing the current experimental API. Finally, someone *might* use the new FS API and we may need to add special case treatment for the data written through it in later releases. So, this is what I plan to do: * Remove the above mentioned API extensions in a single commit, including CHANGES update. * Create a branch from the immediate predecessor revision to keep the code accessible in case we want to reuse bits of it in a later implementation. If you have any objections to this plan, voice them by Wed 1200 UTC. -- Stefan^2.
