You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by rh...@apache.org on 2014/01/11 00:24:04 UTC
svn commit: r1557282 - in /subversion/site/publish/docs/release-notes:
1.7.html 1.8.html
Author: rhuijben
Date: Fri Jan 10 23:24:03 2014
New Revision: 1557282
URL: http://svn.apache.org/r1557282
Log:
* site/publish/docs/release-notes/1.7.html
* site/publish/docs/release-notes/1.8.html
Following up on r1557269, fix small typo.
Modified:
subversion/site/publish/docs/release-notes/1.7.html
subversion/site/publish/docs/release-notes/1.8.html
Modified: subversion/site/publish/docs/release-notes/1.7.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.7.html?rev=1557282&r1=1557281&r2=1557282&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.7.html (original)
+++ subversion/site/publish/docs/release-notes/1.7.html Fri Jan 10 23:24:03 2014
@@ -1582,7 +1582,7 @@ being served from. This happens because
Subversion traffic and sets the Content-Encoding header to specify that the
file has been gziped for transmport without changing the file content. Since
the Subversion client supports gzip content-encoding it decompresses the file
-and ends up with the decompressed file which does not match the cheksum of the
+and ends up with the decompressed file which does not match the checksum of the
file it expected. It is possible that this change may cause other filters to
match Subversion requests that would not have in the past and trigger other
similar errors with other httpd configurations.</p>
Modified: subversion/site/publish/docs/release-notes/1.8.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.8.html?rev=1557282&r1=1557281&r2=1557282&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Fri Jan 10 23:24:03 2014
@@ -2593,7 +2593,7 @@ being served from. This happens because
Subversion traffic and sets the Content-Encoding header to specify that the
file has been gziped for transmport without changing the file content. Since
the Subversion client supports gzip content-encoding it decompresses the file
-and ends up with the decompressed file which does not match the cheksum of the
+and ends up with the decompressed file which does not match the checksum of the
file it expected. It is possible that this change may cause other filters to
match Subversion requests that would not have in the past and trigger other
similar errors with other httpd configurations.</p>