svn commit: r1629879 - /subversion/trunk/subversion/libsvn_fs_fs/fs.c

[st...@apache.org]

Author: stefan2
Date: Tue Oct  7 12:53:38 2014
New Revision: 1629879

URL: http://svn.apache.org/r1629879
Log:
* subversion/libsvn_fs_fs/fs.c
  (fs_open_for_recovery): Explain why we don't check for specific
                          error codes.  No functional change.

Modified:
    subversion/trunk/subversion/libsvn_fs_fs/fs.c

Modified: subversion/trunk/subversion/libsvn_fs_fs/fs.c
URL: http://svn.apache.org/viewvc/subversion/trunk/subversion/libsvn_fs_fs/fs.c?rev=1629879&r1=1629878&r2=1629879&view=diff
==============================================================================
--- subversion/trunk/subversion/libsvn_fs_fs/fs.c (original)
+++ subversion/trunk/subversion/libsvn_fs_fs/fs.c Tue Oct  7 12:53:38 2014
@@ -376,8 +376,14 @@ fs_open_for_recovery(svn_fs_t *fs,
     {
       const char *file_path;
 
-      /* 'current' file is missing or contains garbage.
-       * Start with HEAD = 0 in that case. */
+      /* 'current' file is missing or contains garbage.  Since we are trying
+       * to recover from whatever problem there is, being picky about the
+       * error code here won't do us much good.  If there is a persistent
+       * problem that we can't fix, it will show up when we try rewrite the
+       * file a few lines further below and we will report the failure back
+       * to the caller.
+       *
+       * Start recovery with HEAD = 0. */
       svn_error_clear(err);
       file_path = svn_fs_fs__path_current(fs, subpool);