Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-doc
Navigation:
Lists: gentoo-doc: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-doc@g.o
From: Xavier Neys <neysx@g.o>
Subject: Re: AMD64 HOWTOs
Date: Sun, 07 Aug 2005 18:14:00 +0200
Alin Dobre wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hey everyone,
> 
> Is there a specific reason for the AMD64 HOWTOs [1] not be listed on the
> documentation index page? I'm asking this because if a translator
> translates them (as I consider them quite useful), they won't get listed
> as translated anywhere.
> I understand that GDP is not responsable for the AMD64 project-space
> documentation, and I'm assuming that at least the two AMD64
> documentation developers are subscribed on this list, so they can respond.

AMD64 howtos have been added to our metadoc. Its index will show on our main 
index and list of docs, its files will show up on overview.xml.

I took the liberty of fixing the date format in 2005.0-upgrade-amd64.xml, 
bugs.xml and chroot.xml.
FYI, the date that is displayed on a handbook is the latest date of its index 
and all included chapters, latest being defined as an alphabetical max(date).
If you mix yyyy-mm-dd and English dates in one handbook, the English one will 
always be "later" then the yyyy-mm-dd ones.


Cheers,
-- 
/  Xavier Neys
\_ Gentoo Documentation Project
/  French & Internationalisation Lead
\  http://www.gentoo.org/doc/en
/\
-- 
gentoo-doc@g.o mailing list


References:
AMD64 HOWTOs
-- Alin Dobre
Navigation:
Lists: gentoo-doc: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: AMD64 HOWTOs
Next by thread:
ppc64/2005.1
Previous by date:
Re: AMD64 HOWTOs
Next by date:
ppc64/2005.1


Updated Jun 17, 2009

Summary: Archive of the gentoo-doc mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.