neysx       06/02/26 13:56:07

  Modified:    xml/htdocs/doc/en gentoo-amd64-faq.xml
  Log:
  #124114 Fix link to AMD64 howtos

Revision  Changes    Path
1.13      +4 -4      xml/htdocs/doc/en/gentoo-amd64-faq.xml

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

Index: gentoo-amd64-faq.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- gentoo-amd64-faq.xml        17 Feb 2006 18:48:22 -0000      1.12
+++ gentoo-amd64-faq.xml        26 Feb 2006 13:56:07 -0000      1.13
@@ -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/gentoo-amd64-faq.xml,v 
1.12 2006/02/17 18:48:22 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 
1.13 2006/02/26 13:56:07 neysx Exp $ -->
 
 <guide link="/doc/en/gentoo-amd64-faq.xml">
 <title>Gentoo Linux/AMD64 Frequently Asked Questions</title>
@@ -26,8 +26,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.9</version>
-<date>2006-02-11</date>
+<version>1.10</version>
+<date>2006-02-26</date>
 
 <chapter>
 <title>Questions</title>
@@ -423,7 +423,7 @@
 If you find a bug or you want to send us patches, you need to file a bug
 report. It only takes you a little while, and your help is really appreciated.
 Please follow the <uri
-link="/proj/en/base/amd64/howtos/index.xml?part=1&amp;chap=2">Filing a Bug
+link="/proj/en/base/amd64/howtos/index.xml?part=1&amp;chap=1">Filing a Bug
 Guide</uri>.
 </p>
 



-- 
[email protected] mailing list

Reply via email to