public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jan Kundrat <jkt@stork.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: kde-split-ebuilds.xml
Date: Wed, 16 Jan 2008 18:49:32 +0000	[thread overview]
Message-ID: <E1JFDKO-0000vN-Ed@stork.gentoo.org> (raw)

jkt         08/01/16 18:49:32

  Modified:             kde-split-ebuilds.xml
  Log:
  Update wrt KDE 4.0.0 and current state of the tree

Revision  Changes    Path
1.14                 xml/htdocs/doc/en/kde-split-ebuilds.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.14&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.14&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml?r1=1.13&r2=1.14

Index: kde-split-ebuilds.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- kde-split-ebuilds.xml	24 Jun 2007 00:39:37 -0000	1.13
+++ kde-split-ebuilds.xml	16 Jan 2008 18:49:32 -0000	1.14
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.13 2007/06/24 00:39:37 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.14 2008/01/16 18:49:32 jkt Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
@@ -25,8 +25,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.10</version>
-<date>2007-06-23</date>
+<version>1.11</version>
+<date>2007-01-16</date>
 
 <chapter>
 <title>The Split KDE Ebuilds</title>
@@ -51,7 +51,7 @@
 <p>
 We still provide monolithic ebuilds for 3.5 and they are cleanly interoperable
 with the split ones. However, the split ebuilds are the new default, and there
-will be no monolithic ebuilds for KDE 4.0.
+will be no monolithic ebuilds after KDE 4.0.
 </p>
 
 <p>
@@ -66,9 +66,10 @@
 <body>
 
 <p>
-The latest stable KDE release, as of this writing, is 3.5.5. The latest
-unstable (~arch) is 3.5.7. Split and monolithic ebuilds for both releases are
-present in Portage.
+The latest stable KDE release, as of this writing, is 3.5.7. The latest
+unstable (~arch) is 3.5.8. Split and monolithic ebuilds for both releases are
+present in Portage. The 4.0.0 release is about to enter the tree in hardmasked
+state.
 </p>
 
 <ul>



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



             reply	other threads:[~2008-01-16 18:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 18:49 Jan Kundrat [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-17  0:14 [gentoo-doc-cvs] cvs commit: kde-split-ebuilds.xml Jan Kundrat
2006-12-23  4:06 Josh Saddler
2006-09-28 11:40 Josh Saddler
2006-01-02 10:05 Xavier Neys
2005-11-30 10:28 Xavier Neys
2005-10-30 18:26 Stefano Rossi
2005-09-09  7:26 Shyam Mani

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=E1JFDKO-0000vN-Ed@stork.gentoo.org \
    --to=jkt@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