public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Shyam Mani" <fox2mike@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: lvm2.xml
Date: Wed, 19 Apr 2006 21:39:22 +0000	[thread overview]
Message-ID: <200604192142.k3JLgMPt028242@robin.gentoo.org> (raw)

fox2mike    06/04/19 21:39:22

  Modified:             lvm2.xml
  Log:
  GuideXML fixes. Replaced wrong usage of <c> with <e>. Thanks to Jan Hendrik Grahl [hope I got his name right ;)] <grahl@gentoo.org> for reporting

Revision  Changes    Path
1.20                 xml/htdocs/doc/en/lvm2.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/lvm2.xml?rev=1.20&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/lvm2.xml?rev=1.20&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/lvm2.xml.diff?r1=1.19&r2=1.20&cvsroot=gentoo

Index: lvm2.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/lvm2.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- lvm2.xml	17 Feb 2006 02:53:19 -0000	1.19
+++ lvm2.xml	19 Apr 2006 21:39:22 -0000	1.20
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/lvm2.xml,v 1.19 2006/02/17 02:53:19 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/lvm2.xml,v 1.20 2006/04/19 21:39:22 fox2mike Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/lvm2.xml">
@@ -24,8 +24,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>2.2</version>
-<date>2006-02-06</date>
+<version>2.3</version>
+<date>2006-04-20</date>
 
 <chapter>
 <title>Introduction</title>
@@ -42,7 +42,7 @@
 This document is not intended to be an LVM2 tutorial.  It serves as a
 supplement to the Gentoo installation procedure as described in the <uri
 link="/doc/en/handbook/handbook-x86.xml?part=1">Handbook, Part 1</uri>. Make
-sure you <c>read</c> the Gentoo Installation Manual <c>before</c> you start
+sure you <e>read</e> the Gentoo Installation Manual <e>before</e> you start
 your installation process.
 </warn>
 
@@ -123,8 +123,8 @@
 <body>
 
 <p>
-Follow the handbook, but with the following amendments to chapter <c>4. 
-Preparing the Disks</c>:
+Follow the handbook, but with the following amendments to chapter <e>4. 
+Preparing the Disks</e>:
 </p>
 
 <p>



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



             reply	other threads:[~2006-04-19 21:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-19 21:39 Shyam Mani [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-23 19:49 [gentoo-doc-cvs] cvs commit: lvm2.xml Sven Vermeulen
2007-11-03 21:14 Josh Saddler
2006-02-17  2:53 Lukasz Damentko
2006-02-06 17:12 Xavier Neys
2006-01-20 11:42 Xavier Neys
2005-10-03 22:49 Lukasz Damentko
2005-09-23 13:57 Xavier Neys
2005-08-16 22:30 Xavier Neys

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=200604192142.k3JLgMPt028242@robin.gentoo.org \
    --to=fox2mike@lark.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