Remove the lock release code from the update editor that was introduced in the failure to update code path in r919416. The locks should be released via the access batons for old api-users (like how it worked before) and new code uses an infinite depth approach (or something that looks like that if you don't use SVN_WC__SINGLE_DB. In both cases the update editor should never release locks that it didn't obtain itself.
Remove the lock release code from the update editor that was introduced in the
failure to update code path in r919416. The locks should be released via the
access batons for old api-users (like how it worked before) and new code
uses an infinite depth approach (or something that looks like that if you
don't use SVN_WC__SINGLE_DB. In both cases the update editor should never
release locks that it didn't obtain itself.

* subversion/libsvn_wc/update_editor.c
  (edit_baton): Remove close_edit_complete.
  (cleanup_dir_baton): Remove lock release.
  (close_edit): Don't set close_edit_complete.
  (make_editor): Don't initialize close_edit_complete.


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

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