Markus Schaber <[email protected]> writes: > My current workaround is that my code memorizes all the pathes where a > svn_wc_notify_commit_XXX notifications occurs, and after the commit > operation has finished successfully, it assumes all those pathes have > been unlocked. > > Can someone confirm that this will catch all unlockings? Or do I need > to I re-check using svn_client_status5 to avoid false positives?
Unlocking happens as a separate operation on the server after the commit which means it is possible for unlocking to fail after the commit itself has succeeded. Whether the client finds out about the failure depends on the server implementation. Both mod_dav_svn and svnserve hide the error from the client see: mod_dav_svn/version.c:release_locks svnserve/serve.c:unlock_paths -- Certified & Supported Apache Subversion Downloads: http://www.wandisco.com/subversion/download
