Recipe:
1. user1 begins a transaction against HEAD, and changes some files beneath
a directory /foo/bar
2. user2 begins a transaction against HEAD, and changes a directory property on
/foo/bar
3. user2's commit finishes first
4. user1's commit finishes thereafter
Expected results:
Either that user1's commit is bounced for being out of date, or that user2's
property changes survive user1's commit. (I'm sleepy, so I can't make a good
determination of which one)
Actual results:
user2's property changes last only until user1's commit comes in, after which
the property changes are reverted to the pre-user2-commit state.
That's bad, right?
Blocker 
