Author: philip
Date: Fri Oct  7 14:29:15 2011
New Revision: 1180053

URL: http://svn.apache.org/viewvc?rev=1180053&view=rev
Log:
* docs/release-notes/1.7.html (rhel-2-issue, javahl-issue): Tweak wording.

Modified:
    subversion/site/publish/docs/release-notes/1.7.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=1180053&r1=1180052&r2=1180053&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.7.html (original)
+++ subversion/site/publish/docs/release-notes/1.7.html Fri Oct  7 14:29:15 2011
@@ -1288,7 +1288,7 @@ may be fixed in later 1.7.x releases.</p
 <p>Building Subversion 1.7.0 and APR 1.4.5 from source on 64-bit RHEL2
 with the standard compiler will produce executables that SEGV on
 startup.  This problem is likely to affect all 64-bit x86 platforms
-that use gcc 4.0.x or older.  This is due to APR bug
+that use gcc 4.0.x or older and is due to APR bug
 <a href="https://issues.apache.org/bugzilla/show_bug.cgi?id=51851";>51851</a>.
 Workarounds include using a more recent gcc or configuring APR
 with <tt>--disable-nonportable-atomics</tt>.</p>
@@ -1301,11 +1301,10 @@ with <tt>--disable-nonportable-atomics</
     title="Link to this section">&para;</a>
 </h3>
 
-<p>The JavaHL bindings have moved to the org.apache.subversion
-namespace (what is the correct Java term?) with org.tigris.subversion
-provided as a compatibility layer.  Using the compatibility namespace
-will cause the JVM to SEGV when SVNAdmin or SVNClient objects are
-finalized.  See the 1.7.0
+<p>The JavaHL bindings have moved to the org.apache.subversion package
+with org.tigris.subversion provided as a compatibility layer.  Using
+the compatibility package will cause the JVM to SEGV when SVNAdmin or
+SVNClient objects are finalized.  See the 1.7.0
 <a 
href="http://svn.apache.org/repos/asf/subversion/tags/1.7.0/STATUS";>STATUS</a>
 for details of a patch.
 </p>


Reply via email to