Dear Wiki user, You have subscribed to a wiki page or wiki category on "Subversion Wiki" for change notification.
The "Svn19ApiReview" page has been changed by StefanFuhrmann: https://wiki.apache.org/subversion/Svn19ApiReview?action=diff&rev1=13&rev2=14 Comment: Remove entries that got fixed recently. New functions: * `svn_client_vacuum` — Missing documentation for arguments `fix_recorded_timestamps` and `vacuum_pristines`. (svn praise: r1548088 rhuijben) - * `svn_client_cleanup2` — Missing documentation for arguments `fix_recorded_timestamps`, `clear_dav_cache` and `vacuum_pristines`. (svn praise: r1548088 rhuijben) - * `svn_client_cleanup` — Missing SVN_DEPRECATED annotation. === svn_diff.h === * `svn_diff_output2` @@ -29, +27 @@ === svn_fs.h === * `svn_fs_commit_txn` — Is the `SVN_FS_TXN_CLIENT_DATE` behavior still as described? Do we want to mention here that this is a 1.9 extension? - * `svn_fs_dir_optimal_order` — Should use 2 pools as its implementation creates temporary objects. * `svn_fs_lock_target_create` — `pool` parameter: Is this a `result_pool` or should it even become 2 pools? * `svn_fs_lock_callback_t` — `pool` parameter: Maybe rename to `scratch_pool`. * `svn_fs_lock_many`, `svn_fs_unlock_many` — Mention in docstring that these are not atomic operations. If the callback returns an error, they simply return that error to their callers and leave part of the locks in their initial and the remainder in the final state. What is the lock error handling in case of `lock_callback==NULL`?
