You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by br...@apache.org on 2013/08/28 22:22:51 UTC
svn commit: r1518362 - /subversion/site/publish/docs/release-notes/1.8.html
Author: breser
Date: Wed Aug 28 20:22:51 2013
New Revision: 1518362
URL: http://svn.apache.org/r1518362
Log:
* publish/docs/release-notes/1.8.html: Fix a bunch of HTML errors.
Modified:
subversion/site/publish/docs/release-notes/1.8.html
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=1518362&r1=1518361&r2=1518362&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Wed Aug 28 20:22:51 2013
@@ -341,7 +341,7 @@ Schedule: delete
</div>
<div class="h4" id="svn-info">
-<h4><tt>svn info</tt> now shows repository-relative URLs</tt>
+<h4><tt>svn info</tt> now shows repository-relative URLs
<a class="sectionlink" href="#svn-info"
title="Link to this section">¶</a>
</h4>
@@ -1208,6 +1208,7 @@ may need to be read during a checkout. T
cache is similar to that for the other caches: <tt>svnserve</tt>
now accepts the <tt>--cache-revprops yes</tt> parameter. For
<tt>mod_dav_svn</tt>, the same looks like this in <tt>httpd.conf</tt>
+</p>
<pre>
<IfModule dav_svn_module>
@@ -1586,7 +1587,7 @@ working copy's meta data area inside the
Before Subversion 1.8, pristine data was always downloaded from
the server even if the same data already existed in the cache.</p>
-Subversion 1.8 avoids downloading pristine content that is already
+<p>Subversion 1.8 avoids downloading pristine content that is already
present in the cache, based on the content's SHA1 or MD5 checksum.
This results in more efficient use of network throughput in cases where
a lot of files in the working copy share the same content (for example,
@@ -1721,7 +1722,7 @@ your changes have effected the permissio
<p><tt>svnauthz accessof</tt> supports <tt>--username</tt>,
<tt>--repository</tt>, and <tt>--path</tt> arguments.
-When these are passed, it prints <tt>no</tt>, </tt>r</tt>,
+When these are passed, it prints <tt>no</tt>, <tt>r</tt>,
or <tt>rw</tt> depending on what access the given username has:
none, read-only, or read-write.</p>
@@ -1822,7 +1823,7 @@ Index: bar.c
--- bar.c (.../foo.c) (working copy)
+++ bar.c (.../bar.c) (working copy)
@@ -1,6 +1,6 @@
- #include <stdio.h>
+ #include <stdio.h>
int main()
{
- printf("Hello world!\n");
@@ -1980,7 +1981,7 @@ Documentation</a> page for general API i
probably look at the header files for the interfaces you use and see
what's changed.</p>
-A small number of APIs have slightly changed functionality from their
+<p>A small number of APIs have slightly changed functionality from their
historical roots. Each of these cases has been documented as an
<a href="http://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/1.8/">errata</a>,
detailing the impact of these changes. All of the errata were the result of
@@ -2430,7 +2431,7 @@ file:</p>
exclusive-locking-clients = svn
</pre>
-<p>or by using the command line option <tt>--config-option config:working-copy:exclusive-locking-clients=svn</tt>.
+<p>or by using the command line option <tt>--config-option config:working-copy:exclusive-locking-clients=svn</tt>.</p>
<p>This reduces the locking overhead but does mean that only one
Subversion client will be able to access the working copy at a time. A
@@ -2549,22 +2550,23 @@ undesired side effects.</p>
<ul>
<li><tt><Directory></tt> blocks could match requests being served by
mod_dav_svn. This would allow directives applied in these configuration
- blocks (most notably access control directives) to be applied.
+ blocks (most notably access control directives) to be applied.</li>
<li>When using Apache httpd 2.4.x and <tt>mod_dir</tt>, if a file from the
<tt>DirectoryIndex</tt> directive existed at the path Apache httpd believed
it was serving then the request would be rewritten to access that file,
which may or may not exist. If the path was the <tt>SVNParentPath</tt>
then SVN would try to access a repository with the name of the
- <tt>DirectoryIndex</tt> file that was found.
+ <tt>DirectoryIndex</tt> file that was found.</li>
<li>When using the <tt>%f</tt> variable in your log directives you would log
the path constructed as described above. This was confusing since it was
- not the content that was actually served.
+ not the content that was actually served.</li>
</ul>
<p>Starting with Subversion 1.7.12 and 1.8.2 the requests being served by
<tt>mod_dav_svn</tt> will not be mapped to the local file system and when
logging with the <tt>%f</tt> variable you will see a <tt>"-"</tt>
logged. <tt><Directory></tt> blocks will no longer apply to such requests.
+</p>
<div class="notice">
<p><span style="color: red"><b>WARNING:</b></span>Therefore, if you were