From: "Joshua Saddler (nightmorph)" <nightmorph@gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: ipv6.xml
Date: Mon, 5 Jul 2010 23:35:50 +0000 (UTC) [thread overview]
Message-ID: <20100705233550.443312CE14@corvid.gentoo.org> (raw)
nightmorph 10/07/05 23:35:50
Modified: ipv6.xml
Log:
clean up the ipv6 guide for totd; use modern keywording syntax. soon it should be stabilized, too, which means removing the keyword steps.
Revision Changes Path
1.32 xml/htdocs/doc/en/ipv6.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/ipv6.xml?rev=1.32&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/ipv6.xml?rev=1.32&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/ipv6.xml?r1=1.31&r2=1.32
Index: ipv6.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/ipv6.xml,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- ipv6.xml 15 Mar 2010 21:47:54 -0000 1.31
+++ ipv6.xml 5 Jul 2010 23:35:49 -0000 1.32
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ipv6.xml,v 1.31 2010/03/15 21:47:54 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ipv6.xml,v 1.32 2010/07/05 23:35:49 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide>
@@ -20,6 +20,9 @@
<author title="Editor">
<mail link="okun@hack.fi">Pasi Valminen</mail>
</author>
+<author title="Editor">
+ <mail link="nightmorph"/>
+</author>
<abstract>
This guide shows how to setup IPv6 on a Gentoo system. This includes
@@ -29,8 +32,8 @@
<license/>
-<version>1.8</version>
-<date>2010-03-15</date>
+<version>1.9</version>
+<date>2010-07-05</date>
<chapter>
<title>Preliminaries</title>
@@ -763,14 +766,13 @@
</p>
<p>
-Since <c>totd</c> is still <c>~x86</c> masked pending further testing, you'll
-have to unmask it by appending the following line to your
-<path>/etc/portage/package.keywords</path> file (see "man portage" for more
-informations about this file).
+Since <c>totd</c> is still in <c>~arch</c>, you'll have to keyword it by
+appending the following line to your <path>/etc/portage/package.keywords</path>
+file (see "man portage" for more information about this file).
</p>
-<pre caption="Permanently unmask totd in package.keywords">
-net-misc/totd ~x86
+<pre caption="Add totd to package.keywords">
+net-misc/totd
</pre>
<p>
next reply other threads:[~2010-07-05 23:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 23:35 Joshua Saddler (nightmorph) [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-22 13:30 [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: ipv6.xml Sven Vermeulen (swift)
2011-09-02 19:49 Sven Vermeulen (swift)
2011-07-25 5:15 Joshua Saddler (nightmorph)
2011-07-24 18:56 Joshua Saddler (nightmorph)
2011-07-15 5:51 Joshua Saddler (nightmorph)
2011-03-02 9:53 Joshua Saddler (nightmorph)
2010-08-12 6:20 Joshua Saddler (nightmorph)
2010-07-18 19:02 Joshua Saddler (nightmorph)
2010-07-18 18:51 Joshua Saddler (nightmorph)
2010-07-13 17:23 Joshua Saddler (nightmorph)
2010-03-15 21:47 Joshua Saddler (nightmorph)
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=20100705233550.443312CE14@corvid.gentoo.org \
--to=nightmorph@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