public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mart Raudsepp (leio)" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/desktop/gnome/howtos: gnome-2.22-upgrade.xml
Date: Thu, 03 Apr 2008 01:10:10 +0000	[thread overview]
Message-ID: <E1JhDxy-0004qr-99@stork.gentoo.org> (raw)

leio        08/04/03 01:10:10

  Modified:             gnome-2.22-upgrade.xml
  Log:
  Capitalize GNOME everywhere where appropriate - It's GNOME, not Gnome or anything else when referring to the desktop or project

Revision  Changes    Path
1.4                  xml/htdocs/proj/en/desktop/gnome/howtos/gnome-2.22-upgrade.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/gnome/howtos/gnome-2.22-upgrade.xml?rev=1.4&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/gnome/howtos/gnome-2.22-upgrade.xml?rev=1.4&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/gnome/howtos/gnome-2.22-upgrade.xml?r1=1.3&r2=1.4

Index: gnome-2.22-upgrade.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/gnome/howtos/gnome-2.22-upgrade.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- gnome-2.22-upgrade.xml	2 Apr 2008 20:34:40 -0000	1.3
+++ gnome-2.22-upgrade.xml	3 Apr 2008 01:10:09 -0000	1.4
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/gnome/howtos/gnome-2.22-upgrade.xml,v 1.3 2008/04/02 20:34:40 dang Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/gnome/howtos/gnome-2.22-upgrade.xml,v 1.4 2008/04/03 01:10:09 leio Exp $ -->
 
 <guide link="/proj/en/desktop/gnome/howtos/gnome-2.22-upgrade.xml">
 
@@ -8,6 +8,9 @@
 <author title="Author">
   <mail link="remi@gentoo.org">Rémi Cardona</mail>
 </author>
+<author title="Editor">
+  <mail link="leio@gentoo.org">Mart Raudsepp</mail>
+</author>
 
 <abstract>
 This is a guide for upgrading from GNOME 2.20.x to GNOME 2.22.x.
@@ -28,26 +31,26 @@
 
 <p>
 Starting with 2.22, Seahorse (app-crypt/seahorse) is the blessed key and
-password manager, replacing the old and tired Gnome Keyring Manager
+password manager, replacing the old and tired GNOME Keyring Manager
 (gnome-extra/gnome-keyring-manager). It handles both GPG and SSH keys, and can
-be also used to manage the passwords saved in your Gnome keyring.
+be also used to manage the passwords saved in your GNOME keyring.
 </p>
 
 </body>
 </section>
 <section>
-<title>PAM and Gnome Keyring integration</title>
+<title>PAM and GNOME Keyring integration</title>
 <body>
 
 <p>
-Starting with Gnome 2.20, Gnome Keyring (gnome-base/gnome-keyring) started
+Starting with GNOME 2.20, GNOME Keyring (gnome-base/gnome-keyring) started
 providing a PAM module (pam_gnome_keyring.so) to automatically unlock your
 keyring as you log in to your session, thereby saving you the trouble from
 typing two passwords.
 </p>
 
 <p>
-In Gnome 2.22, this feature is now even more easily configured, thanks to
+In GNOME 2.22, this feature is now even more easily configured, thanks to
 sys-auth/pambase that sports a shiny gnome use flag. With this flag enabled,
 the pam configuration files in /etc/pam.d/ will automatically have
 pam_keyring.so inserted in the right places. Just remember to use "etc-update"
@@ -69,14 +72,14 @@
 
 <p>
 Unfortunately, that code still is not ready for production use (at the time of
-writing, it is in an alpha stage) so the Gnome release managers decided not to
-include GDM 2.22 for Gnome 2.22, but to ship GDM 2.20 instead. Ubuntu and
+writing, it is in an alpha stage) so the GNOME release managers decided not to
+include GDM 2.22 for GNOME 2.22, but to ship GDM 2.20 instead. Ubuntu and
 Mandriva are both going to be using GDM 2.20 for their Spring 2008 releases, we
 also decided to include that version in portage.
 </p>
 
 <p>
-During the Gnome 2.23/2.24 testing cycle, we will probably package the new GDM
+During the GNOME 2.23/2.24 testing cycle, we will probably package the new GDM
 if we feel that the featureset is consistent with the old version and that
 migration does not come with too high a price.
 </p>
@@ -99,11 +102,11 @@
 <chapter>
 <title>Known Issues</title>
 <section>
-<title>Gnome no longer available as a session option in GDM</title>
+<title>GNOME no longer available as a session option in GDM</title>
 <body>
 
 <note>
-This section should only concern users of the Gnome overlay. Users who have been using Gnome 2.22 from Portage should be fine.
+This section should only concern users of the GNOME overlay. Users who have been using GNOME 2.22 from Portage should be fine.
 </note>
 
 <p>
@@ -111,11 +114,11 @@
 </p>
 
 <p>
-In Gnome 2.20, the file /usr/share/xsessions/gnome.desktop was installed by GDM, which causes a lot of headaches. For instance, if you want to use another login manager (such as KDM or Entrance) capable of reading .desktop files but still use a Gnome session, you would have to install GDM even if you never used it.
+In GNOME 2.20, the file /usr/share/xsessions/gnome.desktop was installed by GDM, which causes a lot of headaches. For instance, if you want to use another login manager (such as KDM or Entrance) capable of reading .desktop files but still use a GNOME session, you would have to install GDM even if you never used it.
 </p>
 
 <p>
-In Gnome 2.22, that small issue was fixed and the gnome.desktop file is now installed by gnome-base/gnome-session (which is the actual program launched by the login manager to start Gnome).
+In GNOME 2.22, that small issue was fixed and the gnome.desktop file is now installed by gnome-base/gnome-session (which is the actual program launched by the login manager to start GNOME).
 </p>
 
 <p>



-- 
gentoo-commits@lists.gentoo.org mailing list



             reply	other threads:[~2008-04-03  1:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03  1:10 Mart Raudsepp (leio) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-06-21 17:15 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/desktop/gnome/howtos: gnome-2.22-upgrade.xml Remi Cardona (remi)
2008-06-20  6:45 Remi Cardona (remi)
2008-04-03  5:36 Joshua Saddler (nightmorph)
2008-04-03  1:59 Mart Raudsepp (leio)
2008-04-03  1:53 Mart Raudsepp (leio)
2008-04-03  1:42 Mart Raudsepp (leio)
2008-04-03  1:40 Mart Raudsepp (leio)
2008-04-03  1:31 Mart Raudsepp (leio)
2008-04-03  1:24 Mart Raudsepp (leio)
2008-04-03  1:12 Mart Raudsepp (leio)
2008-04-02 20:34 Daniel Gryniewicz (dang)
2008-04-01 22:00 Remi Cardona (remi)
2008-03-30 20:53 Remi Cardona (remi)

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=E1JhDxy-0004qr-99@stork.gentoo.org \
    --to=leio@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