mod_dav_svn tries to be smarter than libsvn_repos by forbidding calls to svn_repos_set_path3 with SVN_INVALID_REVNUM, despite the fact that svn_repos_set_path3 explicitly says in its documentation that such calls can be legal.  (Specifically, in the case of a local add (although svn_wc_crawl_revisions3 does not send these), or for hypothetical svn_depth_exclude calls.)  Let's not be so judgmental.
mod_dav_svn tries to be smarter than libsvn_repos by forbidding calls
to svn_repos_set_path3 with SVN_INVALID_REVNUM, despite the fact that
svn_repos_set_path3 explicitly says in its documentation that such
calls can be legal.  (Specifically, in the case of a local add
(although svn_wc_crawl_revisions3 does not send these), or for
hypothetical svn_depth_exclude calls.)  Let's not be so judgmental.

* subversion/mod_dav_svn/reports/update.c
  (dav_svn__update_report): Only raise a "no rev attribute" error if
   the attribute was really missing, not if it's explicitly
   SVN_INVALID_REVNUM (-1).


git-svn-id: f8a4e5e023278da1e04e203c7fe051e3c4285d88@868132 13f79535-47bb-0310-9956-ffa450edef68

YueLinHo/Subversion,YueLinHo/Subversion,YueLinHo/Subversion,YueLinHo/Subversion,YueLinHo/Subversion,YueLinHo/Subversion,YueLinHo/Subversion,wbond/subversion,wbond/subversion,wbond/subversion,wbond/subversion,wbond/subversion,wbond/subversion,YueLinHo/Subversion,wbond/subversion