From: Mart Raudsepp <leio@gentoo.org>
To: gentoo devs <gentoo-dev@lists.gentoo.org>
Cc: pr@gentoo.org
Subject: [gentoo-dev] News Item: GNOME 2.26 upgrade
Date: Tue, 06 Oct 2009 02:11:55 +0300 [thread overview]
Message-ID: <1254784315.2724.2.camel@localhost> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 246 bytes --]
Hello,
See attached news item for consideration.
Suggestions on how to improve it, including the text section, very
welcome.
--
Mart Raudsepp
Gentoo Developer
Mail: leio@gentoo.org
Weblog: http://planet.gentoo.org/developers/leio
[-- Attachment #1.2: 2009-10-06-gnome-226.en.txt --]
[-- Type: text/plain, Size: 818 bytes --]
Title: Upgrade to GNOME 2.26
Author: Gentoo Gnome Team <gnome@gentoo.org>
Content-Type: text/plain
Posted: 2009-10-06
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: <gnome-base/gnome-2.26.0
Display-If-Installed: <gnome-base/gnome-light-2.26.0
Display-If-Installed: <gnome-base/gnome-session-2.26.2
Display-If-Installed: <gnome-base/gnome-menus-2.26.2
We're pleased to announce the stabilization of GNOME-2.26. Users
are strongly encouraged to read the GNOME 2.26 Upgrade Guide, to
avoid or know beforehand any possible issues relating to the
upgrade, such as Applications menu items disappearing, or nautilus
constantly restarting when it is configured to not handle the
desktop.
You may find the Upgrade Guide available online at
http://gnome.gentoo.org/howtos/gnome-2.26-upgrade.xml
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-10-05 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 23:11 Mart Raudsepp [this message]
2009-10-06 11:02 ` [gentoo-dev] News Item: GNOME 2.26 upgrade Mart Raudsepp
2009-10-06 11:21 ` Rémi Cardona
2009-10-07 0:54 ` Nirbheek Chauhan
2009-10-07 1:08 ` Mart Raudsepp
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=1254784315.2724.2.camel@localhost \
--to=leio@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=pr@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