You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by cm...@apache.org on 2011/01/07 21:08:04 UTC
svn commit: r1056482 - /subversion/trunk/subversion/include/svn_fs.h
Author: cmpilato
Date: Fri Jan 7 20:08:04 2011
New Revision: 1056482
URL: http://svn.apache.org/viewvc?rev=1056482&view=rev
Log:
Another followup to r1056468.
* subversion/include/svn_fs.h
(svn_fs_get_locks): Remove note about fixing the BDB problem in the
future. It's fixed.
Modified:
subversion/trunk/subversion/include/svn_fs.h
Modified: subversion/trunk/subversion/include/svn_fs.h
URL: http://svn.apache.org/viewvc/subversion/trunk/subversion/include/svn_fs.h?rev=1056482&r1=1056481&r2=1056482&view=diff
==============================================================================
--- subversion/trunk/subversion/include/svn_fs.h (original)
+++ subversion/trunk/subversion/include/svn_fs.h Fri Jan 7 20:08:04 2011
@@ -2192,7 +2192,8 @@ svn_fs_get_locks2(svn_fs_t *fs,
apr_pool_t *pool);
/** Similar to svn_fs_get_locks2(), but with @a depth always passed as
- * svn_depth_infinity.
+ * svn_depth_infinity, and with the following known problem (which is
+ * not present in svn_fs_get_locks2()):
*
* @note On Berkeley-DB-backed filesystems in Subversion 1.6 and
* prior, the @a get_locks_func callback will be invoked from within a
@@ -2200,8 +2201,7 @@ svn_fs_get_locks2(svn_fs_t *fs,
* as a result, forbidden from calling any svn_fs API functions which
* might themselves attempt to start a new Berkeley DB transaction
* (which is most of this svn_fs API). Yes, this is a nasty
- * implementation detail to have to be aware of. We hope to fix this
- * problem in the future.
+ * implementation detail to have to be aware of.
*
* @deprecated Provided for backward compatibility with the 1.6 API.
*/