subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stef...@apache.org
Subject svn commit: r1463535 - /subversion/trunk/subversion/include/svn_fs.h
Date Tue, 02 Apr 2013 13:38:38 GMT
Author: stefan2
Date: Tue Apr  2 13:38:37 2013
New Revision: 1463535

URL: http://svn.apache.org/r1463535
Log:
Follow-up to r1462828: have another try at clarifying the usage of
@a start and @a end in svn_fs_verify.

* subversion/include/svn_fs.h
  (svn_fs_verify): rephrase docstring

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=1463535&r1=1463534&r2=1463535&view=diff
==============================================================================
--- subversion/trunk/subversion/include/svn_fs.h (original)
+++ subversion/trunk/subversion/include/svn_fs.h Tue Apr  2 13:38:37 2013
@@ -2425,19 +2425,16 @@ svn_fs_pack(const char *db_path,
  * to the Subversion filesystem (mainly the meta-data) located in the
  * directory @a path.  Use @a scratch_pool for temporary allocations.
  *
- * Repository (meta) data forms a tightly knit network of references.
- * A full check can be expensive and may not always be required.  If
- * not equal to #SVN_INVALID_REVNUM, @a start and @a end define the
- * range of revisions to check, with 0 and the current youngest
- * repository revision being the respective default values for these
- * parameters.  However, due to the references among repository (meta)
- * data, the implementation may need to also check elements that are
- * not strictly part of the selected range of revisions.  Thus, it is
- * perfectly legal for a FS implementation to ignore the @a start and
- * @a end parameters entirely.
+ * @a start and @a end define the (minimum) range of revisions to check.
+ * If @a start is #SVN_INVALID_REVNUM, it defaults to @c r0.  Likewise,
+ * @a end will default to the current youngest repository revision when
+ * given as #SVN_INVALID_REVNUM.  Since meta data checks may have to touch
+ * other revisions as well, you may receive notifications for revisions
+ * outside the specified range.   In fact, it is perfectly legal for a FS
+ * implementation to always check all revisions.
  * 
- * Only if @c r0 has been included in the range of revisions to check,
- * are global invariants guaranteed to get verified.
+ * Global invariants are only guaranteed to get verified when @a r0 has
+ * been included in the range of revisions to check.
  *
  * The optional @a notify_func callback is only a general feedback that
  * the operation is still in process but may be called in random revisions



Mime
View raw message