nightmorph    06/02/11 11:46:05

  Modified:    xml/htdocs/doc/en mysql-upgrade-slotted.xml
  Log:
  --master-data=0 added w/author's approval, see bug 121152

Revision  Changes    Path
1.8       +4 -4      xml/htdocs/doc/en/mysql-upgrade-slotted.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/mysql-upgrade-slotted.xml?rev=1.8&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/mysql-upgrade-slotted.xml?rev=1.8&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/mysql-upgrade-slotted.xml.diff?r1=1.7&r2=1.8&cvsroot=gentoo

Index: mysql-upgrade-slotted.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/mysql-upgrade-slotted.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- mysql-upgrade-slotted.xml   11 Feb 2006 10:41:29 -0000      1.7
+++ mysql-upgrade-slotted.xml   11 Feb 2006 11:46:05 -0000      1.8
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/mysql-upgrade-slotted.xml,v 1.7 
2006/02/11 10:41:29 nightmorph Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/mysql-upgrade-slotted.xml,v 1.8 
2006/02/11 11:46:05 nightmorph Exp $ -->
 
 <guide link="/doc/en/mysql-upgrade-slotted.xml">
 <title>Slotted MySQL Upgrade and Migration Guide</title>
@@ -27,8 +27,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>3</version>
-<date>2006-02-02</date>
+<version>4</version>
+<date>2006-02-11</date>
 
 <chapter>
 <title>Upgrading Older MySQL Versions</title>
@@ -136,7 +136,7 @@
   --allow-keywords \
   --flush-logs \
   --hex-blob \
-  --master-data \
+  --master-data \ <comment>(If binary logs are enabled, use --master-data=0 
instead)</comment>
   --max_allowed_packet=16M \
   --quote-names \
   --result-file=BACKUP_MYSQL_4.0.SQL</i>



-- 
[email protected] mailing list

Reply via email to