Our copyfrom deconstruction code relied on an entry's revision being "correctly" set when it decided to remove an extra copyfrom record. However, we altered the conditions around setting the revision in r36909 and that had an unintended ripple effect.
Our copyfrom deconstruction code relied on an entry's revision being
"correctly" set when it decided to remove an extra copyfrom record.
However, we altered the conditions around setting the revision in r36909
and that had an unintended ripple effect.

This clarifies a bunch of comments, and properly rewrites the entry into a
mixed-revision node.

* subversion/libsvn_wc/entries.c:
  (read_entries): ensure we set entry->revision when we elide copyfrom
    records to emulate the old mixed-rev copied subtrees.

jmckaskill/subversion,jmckaskill/subversion,jmckaskill/subversion,jmckaskill/subversion,jmckaskill/subversion,jmckaskill/subversion,jmckaskill/subversion,jmckaskill/subversion