neysx       05/09/23 13:57:32

  Modified:    xml/htdocs/doc/en/handbook/2004.2 hb-install-next.xml
  Log:
  Getting rid of useless part=0 and/or chap=0 in links

Revision  Changes    Path
1.2       +3 -3      xml/htdocs/doc/en/handbook/2004.2/hb-install-next.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2004.2/hb-install-next.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2004.2/hb-install-next.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2004.2/hb-install-next.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo

Index: hb-install-next.xml
===================================================================
RCS file: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2004.2/hb-install-next.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- hb-install-next.xml 15 Nov 2004 12:43:54 -0000      1.1
+++ hb-install-next.xml 23 Sep 2005 13:57:32 -0000      1.2
@@ -4,12 +4,12 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2004.2/hb-install-next.xml,v 1.1 
2004/11/15 12:43:54 swift Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2004.2/hb-install-next.xml,v 1.2 
2005/09/23 13:57:32 neysx Exp $ -->
 
 <sections>
 
 <version>1.13</version>
-<date>October 24, 2004</date>
+<date>2004-10-24</date>
 
 <section>
 <title>Documentation</title>
@@ -25,7 +25,7 @@
 
 <p>
 You should definitely take a look at the next part of the Gentoo Handbook
-entitled <uri link="?part=2&amp;chap=0">Working with Gentoo</uri> which 
explains
+entitled <uri link="?part=2">Working with Gentoo</uri> which explains
 how to keep your software up to date, how to install more software, what USE 
 flags are, how the Gentoo Init system works, etc.
 </p>



-- 
[email protected] mailing list

Reply via email to