From: Sven Vermeulen <swift@stork.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: gentoo-amd64-faq.xml
Date: Wed, 21 May 2008 20:10:04 +0000 [thread overview]
Message-ID: <E1JyudQ-0000cC-E1@stork.gentoo.org> (raw)
swift 08/05/21 20:10:04
Modified: gentoo-amd64-faq.xml
Log:
Coding style
Revision Changes Path
1.27 xml/htdocs/doc/en/gentoo-amd64-faq.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml?rev=1.27&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml?rev=1.27&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml?r1=1.26&r2=1.27
Index: gentoo-amd64-faq.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- gentoo-amd64-faq.xml 25 Aug 2007 09:49:21 -0000 1.26
+++ gentoo-amd64-faq.xml 21 May 2008 20:10:04 -0000 1.27
@@ -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.26 2007/08/25 09:49:21 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.27 2008/05/21 20:10:04 swift Exp $ -->
<guide link="/doc/en/gentoo-amd64-faq.xml">
<title>Gentoo Linux/AMD64 Frequently Asked Questions</title>
@@ -254,10 +254,11 @@
<body>
<p>
-OpenOffice versions prior to 2.0.4 do not build on 64bit systems, so you have to use the
-32bit binary version, available in Portage as <c>app-office/openoffice-bin</c>.
-If you feel brave you can <c>emerge openoffice</c>, but be aware that the 64bit version
-is not yet tested out enough to be considered stable.
+OpenOffice versions prior to 2.0.4 do not build on 64bit systems, so you have to
+use the 32bit binary version, available in Portage as
+<c>app-office/openoffice-bin</c>. If you feel brave you can <c>emerge
+openoffice</c>, but be aware that the 64bit version is not yet tested out
+enough to be considered stable.
</p>
</body>
--
gentoo-doc-cvs@lists.gentoo.org mailing list
next reply other threads:[~2008-05-21 20:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 20:10 Sven Vermeulen [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
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-11 14:22 swift
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=E1JyudQ-0000cC-E1@stork.gentoo.org \
--to=swift@stork.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