Given: A path FOO that is an unedited copied subtree item.
Action: Calling svn_fs_revision_changed() on FOO with cross_copy_history=0
Expected Behavior: Since we don't want to cross copy boundaries, and
since the last thing of interest that occured to FOO was that it was
copied as a child of some parent directory, we would expect that the
list of revisions in which FOO changed (where 'appeared at a location'
counts as a change) would be exactly one item long, and contain only
the revision in which the copy was made.
Actual Behavior: Technically speaking, while traversing the ancestry
data for FOO, we don't cross a copy boundary because FOO has not yet
been lazily migrated to the new copy location. So, instead of getting
a single revision back, we get back all the revisions in which FOO
changed (at least back to the last time a real copy boundary is hit).
Bug
Blocker
