svn commit: r1613667 - /subversion/branches/svn-auth-x509/subversion/libsvn_subr/x509parse.c

[br...@apache.org]

Author: breser
Date: Sat Jul 26 15:56:31 2014
New Revision: 1613667

URL: http://svn.apache.org/r1613667
Log:
On svn-auth-x509 branch, comment fix, no functional change.

* subversion/libsvn_subr/x509parse.c
  (x509name_to_utf8_string): remove a sentence in a comment that no longer
    makes sense in the context of the code.

Modified:
    subversion/branches/svn-auth-x509/subversion/libsvn_subr/x509parse.c

Modified: subversion/branches/svn-auth-x509/subversion/libsvn_subr/x509parse.c
URL: http://svn.apache.org/viewvc/subversion/branches/svn-auth-x509/subversion/libsvn_subr/x509parse.c?rev=1613667&r1=1613666&r2=1613667&view=diff
==============================================================================
--- subversion/branches/svn-auth-x509/subversion/libsvn_subr/x509parse.c (original)
+++ subversion/branches/svn-auth-x509/subversion/libsvn_subr/x509parse.c Sat Jul 26 15:56:31 2014
@@ -758,11 +758,10 @@ x509name_to_utf8_string(const x509_name 
       break;
 
       /* Both BMP and UNIVERSAL should always be in Big Endian (aka
-       * network byte order).  The IANA character set registry says
-       * these character set names should always mean Big Endian.
-       * But rumor has it that there are certs out there with other
-       * endianess and even Byte Order Marks.  If we actually run
-       * into these, we might need to do something about it. */
+       * network byte order).  But rumor has it that there are certs
+       * out there with other endianess and even Byte Order Marks.
+       * If we actually run into these, we might need to do something
+       * about it. */
 
     case ASN1_BMP_STRING:
       SVN_ERR_ASSERT_NO_RETURN(0 == src_string->len % sizeof(apr_uint16_t));