subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s...@apache.org
Subject svn commit: r1794632 - /subversion/trunk/notes/sha1-advisory.txt
Date Tue, 09 May 2017 19:07:09 GMT
Author: stsp
Date: Tue May  9 19:07:09 2017
New Revision: 1794632

URL: http://svn.apache.org/viewvc?rev=1794632&view=rev
Log:
* notes/sha1-advisory.txt: wording tweak

Modified:
    subversion/trunk/notes/sha1-advisory.txt

Modified: subversion/trunk/notes/sha1-advisory.txt
URL: http://svn.apache.org/viewvc/subversion/trunk/notes/sha1-advisory.txt?rev=1794632&r1=1794631&r2=1794632&view=diff
==============================================================================
--- subversion/trunk/notes/sha1-advisory.txt (original)
+++ subversion/trunk/notes/sha1-advisory.txt Tue May  9 19:07:09 2017
@@ -27,8 +27,8 @@ Details:
 
   If both of these files are committed to a Subversion repository, Subversion
   de-duplicates content based on the SHA1 checksum and only the content of
-  one of the files ends up being stored in the repository. However, the meta
-  data stores the MD5 checksums of both files, and these MD5 checksums differ.
+  one of the files ends up being stored in the repository. However, meta data
+  stores the MD5 checksums of both files, and these MD5 checksums differ.
   This causes problems when Subversion eventually uses the MD5 checksum of
   the content which was not in fact stored. For example, updates and commits
   may no longer be possible due to an apparent checksum error.



Mime
View raw message