List:Commits« Previous MessageNext Message »
From:jon Date:April 26 2007 7:59am
Subject:svn commit - mysqldoc@docsrva: r6202 - trunk/refman-5.1
View as plain text  
Author: jstephens
Date: 2007-04-26 09:59:17 +0200 (Thu, 26 Apr 2007)
New Revision: 6202

Log:

Wrong word (Thanks, Tomas!)



Modified:
   trunk/refman-5.1/mysql-cluster-mccge.xml
   trunk/refman-5.1/mysql-cluster-merged.xml
   trunk/refman-5.1/mysql-cluster.xml


Modified: trunk/refman-5.1/mysql-cluster-mccge.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-mccge.xml	2007-04-25 23:35:52 UTC (rev 6201)
+++ trunk/refman-5.1/mysql-cluster-mccge.xml	2007-04-26 07:59:17 UTC (rev 6202)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 823 bytes

@@ -17033,7 +17033,7 @@
             <literal>0</literal>. (This is generally true of MySQL
             Cluster and not limited to replication scenarios involving
             Cluster.) The MySQL servers involved in replication should
-            in this case be replicated. After this, you should use the
+            in this case be restarted. After this, you should use the
             <literal>RESET MASTER</literal> and <literal>RESET
             SLAVE</literal> statements to clear the invalid
             <literal>ndb_binlog_index</literal> and


Modified: trunk/refman-5.1/mysql-cluster-merged.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-merged.xml	2007-04-25 23:35:52 UTC (rev 6201)
+++ trunk/refman-5.1/mysql-cluster-merged.xml	2007-04-26 07:59:17 UTC (rev 6202)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 826 bytes

@@ -17554,7 +17554,7 @@
             <literal>0</literal>. (This is generally true of MySQL
             Cluster and not limited to replication scenarios involving
             Cluster.) The MySQL servers involved in replication should
-            in this case be replicated. After this, you should use the
+            in this case be restarted. After this, you should use the
             <literal>RESET MASTER</literal> and <literal>RESET
             SLAVE</literal> statements to clear the invalid
             <literal>ndb_binlog_index</literal> and


Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml	2007-04-25 23:35:52 UTC (rev 6201)
+++ trunk/refman-5.1/mysql-cluster.xml	2007-04-26 07:59:17 UTC (rev 6202)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 805 bytes

@@ -17363,7 +17363,7 @@
             <literal>0</literal>. (This is generally true of MySQL
             Cluster and not limited to replication scenarios involving
             Cluster.) The MySQL servers involved in replication should
-            in this case be replicated. After this, you should use the
+            in this case be restarted. After this, you should use the
             <literal>RESET MASTER</literal> and <literal>RESET
             SLAVE</literal> statements to clear the invalid
             <literal>ndb_binlog_index</literal> and


Thread
svn commit - mysqldoc@docsrva: r6202 - trunk/refman-5.1jon26 Apr