A user reported an assertion failure in 1.7: http://subversion.tigris.org/issues/show_bug.cgi?id=4042
caused by committing a property change on a presence=incomplete directory. It's not possible to prevent property modifications on incomplete directories, since the modification could be made before the directory becomes incomplete. In 1.6 such a commit was allowed and, provided the server accepted the commit, the directory remained incomplete in the working copy. Should we support that in 1.7? Or should we simply have the client refuse to commit incomplete nodes. Most incomplete nodes occur after an interrupted update, but wc could have incomplete working nodes resulting from a wc-wc copy. -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com
