From: Xavier Neys <neysx@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: GLEP 42 (Was: Getting Important Updates To Users)
Date: Fri, 04 Nov 2005 15:26:54 +0100 [thread overview]
Message-ID: <436B6FAE.5040506@gentoo.org> (raw)
In-Reply-To: <436AB50B.2000403@ieee.org>
Nathan L. Adams wrote:
> One source: http://errata.gentoo.org/
>
> Push that out to as many alternate sources as you like (RSS feeds,
> summaries in emerge --news, forums post, etc.), but make it known that
> the website is *the* source (your alternate sources should point back to
> it).
I beg to differ. The tree should be the central point because it's the only
known place where all users can receive relevant information on and for each
and every system they maintain right before they upgrade.
The warning and the logic that triggers its display should be part of Portage.
Sometimes, all that would need to be displayed is "run foo to fix bar" or
"Please do read http://bleh _before_ you upgrade foo".
If an "Upgrade guide to foo/bar for Gentoo" is required, you need an author to
write it, not extra code or an extra web site.
--
/ Xavier Neys
\_ Gentoo Documentation Project
/ French & Internationalisation Lead
\ http://www.gentoo.org/doc/en
/\
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-04 14:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 23:36 [gentoo-dev] GLEP 42 (Was: Getting Important Updates To Users) Chris White
2005-10-31 23:41 ` [gentoo-dev] " Dan Meltzer
2005-10-31 23:52 ` Dan Meltzer
2005-11-01 7:56 ` Wernfried Haas
2005-11-01 14:32 ` Chris Gianelloni
2005-11-01 19:32 ` Stuart Herbert
2005-11-01 19:51 ` Chris Gianelloni
2005-11-03 19:40 ` Stuart Herbert
2005-11-04 1:10 ` Nathan L. Adams
2005-11-04 8:22 ` Sami Näätänen
2005-11-04 14:26 ` Xavier Neys [this message]
2005-11-04 16:44 ` Jason Stubbs
2005-11-04 18:53 ` Alec Joseph Warner
2005-11-05 5:08 ` Jason Stubbs
2005-11-05 5:34 ` Alec Warner
2005-11-07 10:11 ` Paul de Vrieze
2005-11-07 12:37 ` Jason Stubbs
2005-11-07 16:06 ` Grant Goodyear
2005-11-07 16:44 ` Jason Stubbs
2005-11-07 16:43 ` Stuart Herbert
2005-11-05 9:58 ` [gentoo-dev] " Duncan
2005-11-05 12:54 ` [gentoo-dev] " Michiel de Bruijne
2005-11-06 19:32 ` R Hill
2005-11-01 19:53 ` Mike Williams
2005-10-31 23:46 ` [gentoo-dev] " Brian Harring
2005-11-01 10:51 ` Jason Stubbs
2005-11-01 0:42 ` Ciaran McCreesh
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=436B6FAE.5040506@gentoo.org \
--to=neysx@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