You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by lu...@apache.org on 2015/09/16 01:48:30 UTC

svn propchange: r1702974 - svn:log

Author: luke1410
Revision: 1702974
Modified property: svn:log

Modified: svn:log at Tue Sep 15 23:48:30 2015
------------------------------------------------------------------------------
--- svn:log (original)
+++ svn:log Tue Sep 15 23:48:30 2015
@@ -4,10 +4,9 @@ almost as ugly, but better to diagnose e
 Somehow these few cases which should be completely impossible to trigger
 without editing wc.db are reported as TortoiseSVN exception reports.
 
-I explicitly only add these extra checks only to the most common read
-operation, as this function is usually called first and catching every
-invalid working copy database is impossible without a performance and
-a maintenance impact.
+I explicitly add these extra checks only to the most common read operation,
+as this function is usually called first and catching every invalid working
+copy database is impossible without a performance and a maintenance impact.
 
 * subversion/libsvn_subr/token.c
   (svn_token__from_word_err): Ensure NULL is handled safely.