* subversion/libsvn_wc/adm_ops.c   (revert_restore): Ok, thinking this over at 4 AM. I don't think we are     willing to accept the performance regression of r1101473 in svn revert -R.     So I accept that we don't have to revert that are not strictly as checked     out, but are still unmodified according to status.
* subversion/libsvn_wc/adm_ops.c
  (revert_restore): Ok, thinking this over at 4 AM. I don't think we are
    willing to accept the performance regression of r1101473 in svn revert -R.
    So I accept that we don't have to revert that are not strictly as checked
    out, but are still unmodified according to status.

    In most cases this reverts to the behavior of before r1101473, as before
    that we accepted recorded information as 'the file is not modified'. But
    I'm introducing the change now that when the file might be modified, we
    do the less strict comparison.

    The only way to have both the performance and the strict comparison would
    be to store another boolean with the recorded information to tell to what
    level we performed the recorded comparison.
    (And should we then cache the strict or the not strict?)


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

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