public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: "swift" <swift@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: gentoo-amd64-faq.xml
Date: Sat, 11 Feb 2006 14:22:50 +0000	[thread overview]
Message-ID: <200602111422.k1BEMpcN003578@robin.gentoo.org> (raw)

swift       06/02/11 14:22:50

  Modified:    xml/htdocs/doc/en gentoo-amd64-faq.xml
  Log:
  Link to correct location for 32bit guide, thanks to Mark Tabash for noticing

Revision  Changes    Path
1.11      +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.11&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.11&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.10&r2=1.11&cvsroot=gentoo

Index: gentoo-amd64-faq.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- gentoo-amd64-faq.xml	1 Feb 2006 09:45:29 -0000	1.10
+++ gentoo-amd64-faq.xml	11 Feb 2006 14:22:50 -0000	1.11
@@ -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.10 2006/02/01 09:45:29 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.11 2006/02/11 14:22:50 swift 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.7</version>
-<date>2006-02-01</date>
+<version>1.8</version>
+<date>2006-02-11</date>
 
 <chapter>
 <title>Questions</title>
@@ -248,7 +248,7 @@
 
 <p>
 Please read the <uri
-link="/proj/en/base/amd64/howtos/index.xml?part=1&amp;chap=3">32-bit chroot
+link="/proj/en/base/amd64/howtos/index.xml?part=1&amp;chap=2">32-bit chroot
 guide</uri>.
 </p>
 



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



             reply	other threads:[~2006-02-11 14:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-11 14:22 swift [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-09-10 19:46 [gentoo-doc-cvs] cvs commit: gentoo-amd64-faq.xml Joshua Saddler
2008-09-02  7:47 Joshua Saddler
2008-07-25 18:55 Joshua Saddler
2008-05-21 20:10 Sven Vermeulen
2006-11-24 14:47 Josh Saddler
2006-10-25 12:54 Xavier Neys
2006-10-06 22:01 Josh Saddler
2006-10-05  0:00 Josh Saddler
2006-10-04 14:23 Xavier Neys
2006-09-18  8:25 Josh Saddler
2006-09-18  6:53 Josh Saddler
2006-06-17  7:04 Shyam Mani
2006-03-28 10:20 Xavier Neys
2006-03-19 22:26 Jan Kundrat
2006-02-26 13:56 Xavier Neys
2006-02-17 18:48 Shyam Mani
2006-02-01  9:45 Shyam Mani
2005-12-13 12:17 Xavier Neys
2005-11-23 18:06 Xavier Neys
2005-10-31 13:31 Xavier Neys
2005-09-20  9:13 Lukasz Damentko
2005-09-19 21:50 Lukasz Damentko
2005-08-07 11:15 Alin Dobre
2005-07-16 15:14 Jonathan Smith
2005-07-16 15:08 Jonathan Smith
2005-07-16  9:44 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=200602111422.k1BEMpcN003578@robin.gentoo.org \
    --to=swift@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