You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@subversion.apache.org by ph...@apache.org on 2014/04/15 16:16:33 UTC

svn commit: r1587591 - /subversion/trunk/subversion/libsvn_subr/utf_validate.c

Author: philip
Date: Tue Apr 15 14:16:32 2014
New Revision: 1587591

URL: http://svn.apache.org/r1587591
Log:
* subversion/libsvn_subr/utf_validate.c
  (first_non_fsm_start_char_cstring): Fix typo in comment.

Modified:
    subversion/trunk/subversion/libsvn_subr/utf_validate.c

Modified: subversion/trunk/subversion/libsvn_subr/utf_validate.c
URL: http://svn.apache.org/viewvc/subversion/trunk/subversion/libsvn_subr/utf_validate.c?rev=1587591&r1=1587590&r2=1587591&view=diff
==============================================================================
--- subversion/trunk/subversion/libsvn_subr/utf_validate.c (original)
+++ subversion/trunk/subversion/libsvn_subr/utf_validate.c Tue Apr 15 14:16:32 2014
@@ -309,7 +309,7 @@ first_non_fsm_start_char_cstring(const c
 
   /* Scan the input one machine word at a time. */
 #ifndef SVN_UTF_NO_UNINITIALISED_ACCESS
-  /* This may read allocated but initialised bytes beyond the
+  /* This may read allocated but uninitialised bytes beyond the
      terminating null.  Any such bytes are always readable and this
      code operates correctly whatever the uninitialised values happen
      to be.  However memory checking tools such as valgrind and GCC