List:Commits« Previous MessageNext Message »
From:paul Date:January 9 2006 12:09am
Subject:svn commit - mysqldoc@docsrva: r725 - in trunk: . refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: paul
Date: 2006-01-09 01:09:57 +0100 (Mon, 09 Jan 2006)
New Revision: 725

Log:
 r5962@frost:  paul | 2006-01-08 17:34:06 -0600
 Remove extraneous spaces.


Modified:
   trunk/
   trunk/refman-4.1/functions.xml
   trunk/refman-4.1/innodb.xml
   trunk/refman-4.1/ndbcluster.xml
   trunk/refman-5.0/innodb.xml
   trunk/refman-5.0/ndbcluster.xml
   trunk/refman-5.1/innodb.xml
   trunk/refman-5.1/ndbcluster.xml


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:5961
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1994
   + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:5962
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1994

Modified: trunk/refman-4.1/functions.xml
===================================================================
--- trunk/refman-4.1/functions.xml	2006-01-09 00:09:40 UTC (rev 724)
+++ trunk/refman-4.1/functions.xml	2006-01-09 00:09:57 UTC (rev 725)
@@ -8998,7 +8998,7 @@
 
     <para>
       There are no dates between October 4 and October 15. This
-      discontinuity is called the <firstterm>cutover</firstterm> . Any
+      discontinuity is called the <firstterm>cutover</firstterm>. Any
       dates before the cutover are Julian, and any dates following the
       cutover are Gregorian. Dates during a cutover are nonexistent.
     </para>

Modified: trunk/refman-4.1/innodb.xml
===================================================================
--- trunk/refman-4.1/innodb.xml	2006-01-09 00:09:40 UTC (rev 724)
+++ trunk/refman-4.1/innodb.xml	2006-01-09 00:09:57 UTC (rev 725)
@@ -1424,7 +1424,7 @@
 
         <para>
           Normally <literal>InnoDB</literal> uses an algorithm called
-          <firstterm>next-key locking</firstterm> .
+          <firstterm>next-key locking</firstterm>.
           <literal>InnoDB</literal> performs row-level locking in such a
           way that when it searches or scans a table index, it sets
           shared or exclusive locks on any index records it encounters.
@@ -4190,7 +4190,7 @@
 
       <para>
         This is called <firstterm>multi-versioned concurrency
-        control</firstterm> .
+        control</firstterm>.
       </para>
 
       <remark role="todo">
@@ -5738,7 +5738,7 @@
 
       <para>
         <literal>InnoDB</literal> uses a novel file flush technique
-        called <firstterm>doublewrite</firstterm> . It adds safety to
+        called <firstterm>doublewrite</firstterm>. It adds safety to
         recovery following an operating system crash or a power outage,
         and improves performance on most varieties of Unix by reducing
         the need for <literal>fsync()</literal> operations.

Modified: trunk/refman-4.1/ndbcluster.xml
===================================================================
--- trunk/refman-4.1/ndbcluster.xml	2006-01-09 00:09:40 UTC (rev 724)
+++ trunk/refman-4.1/ndbcluster.xml	2006-01-09 00:09:57 UTC (rev 725)
@@ -9320,7 +9320,7 @@
           functional elements of a cluster are referred to as
           <firstterm>nodes</firstterm>, and a computer housing a cluster
           node is sometimes referred to as a <firstterm>cluster
-          host</firstterm> . Ideally, there will be one node per cluster
+          host</firstterm>. Ideally, there will be one node per cluster
           host, although it is possible to run multiple nodes on a
           single host. There are three types of nodes, each
           corresponding to a specific role within the cluster. These
@@ -10380,7 +10380,7 @@
         <para>
           This refers to a logical or functional unit of MySQL Cluster,
           and is sometimes also referred to as a <firstterm>cluster
-          node</firstterm> . In the context of MySQl Cluster, we use the
+          node</firstterm>. In the context of MySQl Cluster, we use the
           term <quote>node</quote> to indicate a
           <emphasis>process</emphasis> rather than a physical component
           of the cluster. There are three node types required to

Modified: trunk/refman-5.0/innodb.xml
===================================================================
--- trunk/refman-5.0/innodb.xml	2006-01-09 00:09:40 UTC (rev 724)
+++ trunk/refman-5.0/innodb.xml	2006-01-09 00:09:57 UTC (rev 725)
@@ -1372,7 +1372,7 @@
 
         <para>
           Normally <literal>InnoDB</literal> uses an algorithm called
-          <firstterm>next-key locking</firstterm> .
+          <firstterm>next-key locking</firstterm>.
           <literal>InnoDB</literal> performs row-level locking in such a
           way that when it searches or scans a table index, it sets
           shared or exclusive locks on any index records it encounters.
@@ -4156,7 +4156,7 @@
 
       <para>
         This is called <firstterm>multi-versioned concurrency
-        control</firstterm> .
+        control</firstterm>.
       </para>
 
       <remark role="todo">
@@ -5683,7 +5683,7 @@
 
       <para>
         <literal>InnoDB</literal> uses a novel file flush technique
-        called <firstterm>doublewrite</firstterm> . It adds safety to
+        called <firstterm>doublewrite</firstterm>. It adds safety to
         recovery following an operating system crash or a power outage,
         and improves performance on most varieties of Unix by reducing
         the need for <literal>fsync()</literal> operations.

Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml	2006-01-09 00:09:40 UTC (rev 724)
+++ trunk/refman-5.0/ndbcluster.xml	2006-01-09 00:09:57 UTC (rev 725)
@@ -9596,7 +9596,7 @@
           functional elements of a cluster are referred to as
           <firstterm>nodes</firstterm>, and a computer housing a cluster
           node is sometimes referred to as a <firstterm>cluster
-          host</firstterm> . Ideally, there will be one node per cluster
+          host</firstterm>. Ideally, there will be one node per cluster
           host, although it is possible to run multiple nodes on a
           single host. There are three types of nodes, each
           corresponding to a specific role within the cluster. These
@@ -10664,7 +10664,7 @@
         <para>
           This refers to a logical or functional unit of MySQL Cluster,
           and is sometimes also referred to as a <firstterm>cluster
-          node</firstterm> . In the context of MySQl Cluster, we use the
+          node</firstterm>. In the context of MySQl Cluster, we use the
           term <quote>node</quote> to indicate a
           <emphasis>process</emphasis> rather than a physical component
           of the cluster. There are three node types required to

Modified: trunk/refman-5.1/innodb.xml
===================================================================
--- trunk/refman-5.1/innodb.xml	2006-01-09 00:09:40 UTC (rev 724)
+++ trunk/refman-5.1/innodb.xml	2006-01-09 00:09:57 UTC (rev 725)
@@ -1366,7 +1366,7 @@
 
         <para>
           Normally <literal>InnoDB</literal> uses an algorithm called
-          <firstterm>next-key locking</firstterm> .
+          <firstterm>next-key locking</firstterm>.
           <literal>InnoDB</literal> performs row-level locking in such a
           way that when it searches or scans a table index, it sets
           shared or exclusive locks on any index records it encounters.
@@ -4132,7 +4132,7 @@
 
       <para>
         This is called <firstterm>multi-versioned concurrency
-        control</firstterm> .
+        control</firstterm>.
       </para>
 
       <remark role="todo">
@@ -5640,7 +5640,7 @@
 
       <para>
         <literal>InnoDB</literal> uses a novel file flush technique
-        called <firstterm>doublewrite</firstterm> . It adds safety to
+        called <firstterm>doublewrite</firstterm>. It adds safety to
         recovery following an operating system crash or a power outage,
         and improves performance on most varieties of Unix by reducing
         the need for <literal>fsync()</literal> operations.

Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml	2006-01-09 00:09:40 UTC (rev 724)
+++ trunk/refman-5.1/ndbcluster.xml	2006-01-09 00:09:57 UTC (rev 725)
@@ -11176,7 +11176,7 @@
           functional elements of a cluster are referred to as
           <firstterm>nodes</firstterm>, and a computer housing a cluster
           node is sometimes referred to as a <firstterm>cluster
-          host</firstterm> . Ideally, there will be one node per cluster
+          host</firstterm>. Ideally, there will be one node per cluster
           host, although it is possible to run multiple nodes on a
           single host. There are three types of nodes, each
           corresponding to a specific role within the cluster. These
@@ -12244,7 +12244,7 @@
         <para>
           This refers to a logical or functional unit of MySQL Cluster,
           and is sometimes also referred to as a <firstterm>cluster
-          node</firstterm> . In the context of MySQl Cluster, we use the
+          node</firstterm>. In the context of MySQl Cluster, we use the
           term <quote>node</quote> to indicate a
           <emphasis>process</emphasis> rather than a physical component
           of the cluster. There are three node types required to

Thread
svn commit - mysqldoc@docsrva: r725 - in trunk: . refman-4.1 refman-5.0 refman-5.1paul9 Jan