From: jon
Date: March 1 2007 4:52am
Subject: svn commit - mysqldoc@docsrva: r5124 - trunk/refman-5.1
List-Archive: http://lists.mysql.com/commits/20860
Message-Id: <200703010452.l214qQTp013315@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Author: jstephens
Date: 2007-03-01 05:52:26 +0100 (Thu, 01 Mar 2007)
New Revision: 5124

Log:

Reformat.



Modified:
   trunk/refman-5.1/news-5.1.xml


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-03-01 04:50:57 UTC (rev 5123)
+++ trunk/refman-5.1/news-5.1.xml	2007-03-01 04:52:26 UTC (rev 5124)
Changed blocks: 2, Lines Added: 29, Lines Deleted: 28; 3863 bytes

@@ -35,45 +35,44 @@
     <filename>TEMPLATE.news.xml</filename> template in the
     <filename>refman-common</filename> directory.
   </remark>
-  
+
   <section id="news-5-1-17">
-    
+
     <title>Changes in release 5.1.17 (Not yet released)</title>
-    
+
     <para role="release-level">
       This is a new Beta development release, fixing recently discovered
-      bugs. 
+      bugs.
     </para>
-    
+
     <para role="release-non-production">
       <emphasis role="bold">NOTE:</emphasis> This Beta release, as any
-      other pre-production 
-      release, should not be installed on <emphasis>production</emphasis>
-      level systems or systems with critical data. It is good practice to
-      back up your data before installing any new version of software.
-      Although MySQL has worked very hard to ensure a high level of
-      quality, protect your data by making a backup as you would for any
-      software beta release. Please refer to our bug database at
-      <ulink url="http://bugs.mysql.com/"/> for more details about the
-      individual bugs fixed in this version.
+      other pre-production release, should not be installed on
+      <emphasis>production</emphasis> level systems or systems with
+      critical data. It is good practice to back up your data before
+      installing any new version of software. Although MySQL has worked
+      very hard to ensure a high level of quality, protect your data by
+      making a backup as you would for any software beta release. Please
+      refer to our bug database at <ulink url="http://bugs.mysql.com/"/>
+      for more details about the individual bugs fixed in this version.
     </para>
-    
+
     <para>
       This section documents all changes and bug fixes that have been
-      applied since the last official MySQL release. If you would like to
-      receive more fine-grained and personalized <emphasis>update
-        alerts</emphasis> about fixes that are relevant to the version and
+      applied since the last official MySQL release. If you would like
+      to receive more fine-grained and personalized <emphasis>update
+      alerts</emphasis> about fixes that are relevant to the version and
       features you use, please consider subscribing to <emphasis>MySQL
-        Network</emphasis> (a commercial MySQL offering). For more details
+      Network</emphasis> (a commercial MySQL offering). For more details
       please see
       <ulink url="http://www.mysql.com/network/advisors.html"/>.
     </para>
-    
+
     <remark role="TODO">
       [js] Uncomment following when there are functionality changes or
       additions to document.
     </remark>
-    
+
 <!--    
     <para>
       Functionality added or changed:

@@ -91,21 +90,23 @@
     <para>
       Bugs fixed:
     </para>
-    
+
     <itemizedlist>
-      
+
       <listitem>
         <para>
           A query of type <literal>index_merge</literal>, and with a
           <literal>WHERE</literal> clause having the form <literal>WHERE
-            <replaceable>indexed_column_1</replaceable>=<replaceable>value_1</replaceable>
-            OR <replaceable>indexed_column_2</replaceable>=<replaceable>value_2</replaceable></literal>
-          on a partitioned table caused the server to crash. (Bug #26117)
+          <replaceable>indexed_column_1</replaceable>=<replaceable>value_1</replaceable>
+          OR
+          <replaceable>indexed_column_2</replaceable>=<replaceable>value_2</replaceable></literal>
+          on a partitioned table caused the server to crash. (Bug
+          #26117)
         </para>
       </listitem>
-      
+
     </itemizedlist>
-    
+
   </section>
 
   <section id="news-5-1-16">