svn commit: r1794629 - /subversion/trunk/notes/sha1-advisory.txt

[st...@apache.org]

Author: stsp
Date: Tue May  9 18:48:11 2017
New Revision: 1794629

URL: http://svn.apache.org/viewvc?rev=1794629&view=rev
Log:
* notes/sha1-advisory.txt: Tweak wording to avoid ambiguity.

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=1794629&r1=1794628&r2=1794629&view=diff
==============================================================================
--- subversion/trunk/notes/sha1-advisory.txt (original)
+++ subversion/trunk/notes/sha1-advisory.txt Tue May  9 18:48:11 2017
@@ -50,7 +50,7 @@ Recommendations:
   copy will run into similar problems: de-duplication of content stored
   in the working copy also relies on SHA1, and for performance reasons
   clients using the HTTP protocol will avoid fetching content with a SHA1
-  checksum which has been stored previously.
+  checksum which has been fetched previously.
 
   Therefore, storing content with SHA1 collisions it not a supported use case.
   If such content needs to be versioned for any reason, consider packing the