public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Saddler <nightmorph@stork.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: gentoo-upgrading.xml
Date: Wed, 05 Mar 2008 08:23:59 +0000	[thread overview]
Message-ID: <E1JWout-0003mB-Lw@stork.gentoo.org> (raw)

nightmorph    08/03/05 08:23:59

  Modified:             gentoo-upgrading.xml
  Log:
  we don't actually have such a table; it was removed for maintainability

Revision  Changes    Path
1.38                 xml/htdocs/doc/en/gentoo-upgrading.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml?rev=1.38&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml?rev=1.38&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml?r1=1.37&r2=1.38

Index: gentoo-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- gentoo-upgrading.xml	7 May 2007 18:11:40 -0000	1.37
+++ gentoo-upgrading.xml	5 Mar 2008 08:23:59 -0000	1.38
@@ -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-upgrading.xml,v 1.37 2007/05/07 18:11:40 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 1.38 2008/03/05 08:23:59 nightmorph Exp $ -->
 
 <guide link="/doc/en/gentoo-upgrading.xml">
 <title>Gentoo Upgrading Guide</title>
@@ -23,8 +23,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>2.8</version>
-<date>2007-05-05</date>
+<version>2.9</version>
+<date>2008-03-05</date>
 
 <chapter>
 <title>Gentoo and Upgrades</title>
@@ -172,8 +172,7 @@
 <p>
 However, Gentoo strongly recommends updating your profile if it becomes 
 deprecated.  When this happens, it means that Gentoo developers no longer
-plan on supporting it. Using the table below, you can quickly check to 
-see what profiles are currently supported.
+plan on supporting it.
 </p>
 
 <p>



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



             reply	other threads:[~2008-03-05  8:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05  8:23 Joshua Saddler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-05  8:26 [gentoo-doc-cvs] cvs commit: gentoo-upgrading.xml Joshua Saddler
2006-11-09  7:00 Josh Saddler
2006-11-08  7:31 Josh Saddler
2006-05-27 13:51 Xavier Neys
2006-02-12 18:59 Lukasz Damentko
2006-02-12 18:51 Lukasz Damentko
2005-12-19 11:49 Jan Kundrat
2005-09-21  8:49 Xavier Neys
2005-09-20 18:24 swift
2005-08-12 10:29 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=E1JWout-0003mB-Lw@stork.gentoo.org \
    --to=nightmorph@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