public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: Lukasz Damentko <rane@stork.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: mysql-upgrading.xml
Date: Mon, 04 Jun 2007 11:03:51 +0000	[thread overview]
Message-ID: <E1HvALn-00084G-Hw@stork.gentoo.org> (raw)

rane        07/06/04 11:03:51

  Modified:             mysql-upgrading.xml
  Log:
  removing a useless quotation mark, thanks to stawrul on irc for reporting

Revision  Changes    Path
1.21                 xml/htdocs/doc/en/mysql-upgrading.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml?rev=1.21&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml?rev=1.21&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml?r1=1.20&r2=1.21

Index: mysql-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- mysql-upgrading.xml	17 May 2007 22:25:45 -0000	1.20
+++ mysql-upgrading.xml	4 Jun 2007 11:03:51 -0000	1.21
@@ -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-upgrading.xml,v 1.20 2007/05/17 22:25:45 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml,v 1.21 2007/06/04 11:03:51 rane Exp $ -->
 
 <guide link="/doc/en/mysql-upgrading.xml">
 <title>Upgrade guide to MySQL 4.* or 5.0.*</title>
@@ -22,8 +22,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.16</version>
-<date>2007-01-06</date>
+<version>1.17</version>
+<date>2007-06-04</date>
 
 <chapter>
 <title>Straight upgrade, suggested for 4.1 =&gt; 5.0 migration</title>
@@ -56,7 +56,7 @@
      <i>| sed -e 's|datadir[ \t]||')</i>
 
 <comment>(This next step should be done in the second shell)</comment>
-# <i>mysql --user=root --password=</i><comment>'your_password'</comment><i>"</i>
+# <i>mysql --user=root --password=</i><comment>'your_password'</comment>
 mysql&gt; <i>FLUSH TABLES WITH READ LOCK;</i>
 
 <comment>(Return to the first shell to run this command)</comment>



-- 
gentoo-doc-cvs@gentoo.org mailing list



             reply	other threads:[~2007-06-04 11:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-04 11:03 Lukasz Damentko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-01-06 21:38 [gentoo-doc-cvs] cvs commit: mysql-upgrading.xml Josh Saddler
2006-12-29  5:49 Josh Saddler
2006-12-04 16:42 Josh Saddler
2006-10-28 11:43 Xavier Neys
2006-09-10 21:27 Josh Saddler
2006-09-10 21:11 Josh Saddler
2006-09-10  1:57 Lukasz Damentko
2006-09-08 11:50 Josh Saddler
2006-09-08 10:39 Xavier Neys
2006-09-08 10:39 Xavier Neys
2006-09-04  9:38 Josh Saddler
2006-03-11 18:26 Josh Saddler
2006-01-04 11:26 Xavier Neys
2005-12-21 11:03 Xavier Neys
2005-10-21 10:11 Xavier Neys
2005-10-17 23:13 Lukasz Damentko
2005-10-17 19:30 Lukasz Damentko
2005-09-21 19:15 Lukasz Damentko
2005-09-11 20:41 Lukasz Damentko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1HvALn-00084G-Hw@stork.gentoo.org \
    --to=rane@stork.gentoo.org \
    --cc=docs-team@lists.gentoo.org \
    --cc=gentoo-doc-cvs@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox