When we delete a newly-added file (and possibly in other situations), we leave behind the WORKING props. Bogus, yes. There is code in svn_wc_add3 to compensate for this, but it needs to axe the files in more situations.
When we delete a newly-added file (and possibly in other situations), we
leave behind the WORKING props. Bogus, yes. There is code in svn_wc_add3
to compensate for this, but it needs to axe the files in more situations.

When propcaching is enabled, we have a boolean indicating whether any
properties exist. If that flag disappears, then we have to rely on the
*presence* of the props file. Thus, we cannot have turds laying around.

If we disable propcaching, then prop_tests 17 fails (add, set prop,
delete, add again; prop should not be present).

* subversion/libsvn_wc/adm_ops.c:
  (svn_wc_add3): delete the WORKING props whether this is a replacement or
    not. generally, they won't be there, but they might...


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

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