[C. Michael Pilato] > Boo! Layer knowledge violation. Ignoring, oh, the tiny percentage > of Subversion code that does something special with r0 props, why > would we special-case this?
It's special because we do ship svnsync officially. (: It's special because r0 never has anything in it _except_ revprops. It's special because it does not get svn:author or svn:log by default like every other revision does. r0 revprops _are_ a natural place to store metadata about the repository as a whole that one does not want to store in the repo filesystem itself. I hardly think svnsync is the only tool that uses it that way. Just as I proposed handling HEAD revprops in a special way to accommodate post-commit hooks that immediately edit their own revision's revprops (the mechanics of this as relates to the implementation of packing is beyond the scope of this message), special-casing the other endpoint, r0, is no less strange. -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/
