From: "Davide Cendron (scen)" <scen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/doc/it: gentoo-amd64-faq.xml
Date: Wed, 15 Apr 2009 19:53:19 +0000 [thread overview]
Message-ID: <E1LuBAd-0002uD-Sq@stork.gentoo.org> (raw)
scen 09/04/15 19:53:19
Modified: gentoo-amd64-faq.xml
Log:
Version 1.23, revision 1.32 of EN CVS
Revision Changes Path
1.16 xml/htdocs/doc/it/gentoo-amd64-faq.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/it/gentoo-amd64-faq.xml?rev=1.16&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/it/gentoo-amd64-faq.xml?rev=1.16&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/it/gentoo-amd64-faq.xml?r1=1.15&r2=1.16
Index: gentoo-amd64-faq.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/it/gentoo-amd64-faq.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- gentoo-amd64-faq.xml 25 Mar 2009 21:38:56 -0000 1.15
+++ gentoo-amd64-faq.xml 15 Apr 2009 19:53:19 -0000 1.16
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/it/gentoo-amd64-faq.xml,v 1.15 2009/03/25 21:38:56 scen Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/it/gentoo-amd64-faq.xml,v 1.16 2009/04/15 19:53:19 scen Exp $ -->
<guide link="/doc/it/gentoo-amd64-faq.xml" lang="it">
<title>Gentoo Linux/AMD64: Domande frequenti (FAQ)</title>
@@ -32,8 +32,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.22</version>
-<date>2009-03-12</date>
+<version>1.23</version>
+<date>2009-04-14</date>
<faqindex>
<title>Domande</title>
@@ -113,8 +113,9 @@
noterà quasi nessuna differenza fra 64-bit e 32-bit. 64-bit è generalmente più
veloce nell'utilizzo di applicazioni che usano la virgola mobile, generalmente
applicazioni multimediali e di rendering 3D. Questo <uri
-link="http://enterprise.linux.com/enterprise/05/06/09/1413209.shtml?tid=121">
-articolo</uri> potrebbe risultare interessante. C'è anche una simpatica <uri
+link="http://www.linux.com/articles/114024?tid=121">articolo</uri> (ed un <uri
+link="http://www.linux.com/feature/43873">articolo collegato</uri>) potrebbe
+risultare interessante. C'è anche una simpatica <uri
link="http://forums.gentoo.org/viewtopic-t-349691.html">discussione</uri> nel
<uri link="http://forums.gentoo.org">forum</uri>.
</p>
next reply other threads:[~2009-04-15 19:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 19:53 Davide Cendron (scen) [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-14 18:02 [gentoo-commits] gentoo commit in xml/htdocs/doc/it: gentoo-amd64-faq.xml Agostino Sarubbo (ago)
2012-05-25 21:20 Agostino Sarubbo (ago)
2012-05-25 19:29 Agostino Sarubbo (ago)
2010-07-29 18:39 Davide Cendron (scen)
2009-06-20 10:23 Davide Cendron (scen)
2009-05-05 19:51 Davide Cendron (scen)
2009-03-25 21:38 Davide Cendron (scen)
2008-09-16 21:49 Davide Cendron (scen)
2008-07-29 20:31 Davide Cendron (scen)
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=E1LuBAd-0002uD-Sq@stork.gentoo.org \
--to=scen@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@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