From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HklgW-0003js-1B for garchives@archives.gentoo.org; Sun, 06 May 2007 18:42:16 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l46IfEJa020261; Sun, 6 May 2007 18:41:14 GMT Received: from randymail-a9.g.dreamhost.com (sd-green-bigip-83.dreamhost.com [208.97.132.83]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l46IdD9H017865 for ; Sun, 6 May 2007 18:39:13 GMT Received: from [192.168.1.4] (c-75-68-33-130.hsd1.nh.comcast.net [75.68.33.130]) by randymail-a9.g.dreamhost.com (Postfix) with ESMTP id 4E5C7EF074 for ; Sun, 6 May 2007 11:39:13 -0700 (PDT) From: Dan Meltzer To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] GLEP 42 news item for review: Radiant upgrade Date: Sun, 6 May 2007 14:39:13 -0400 User-Agent: KMail/1.9.6 References: <1178433936.13701.10.camel@ip6-localhost> <200705061417.29880.hydrogen@notyetimplemented.com> <20070506192102.443d121e@snowflake> In-Reply-To: <20070506192102.443d121e@snowflake> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705061439.13479.hydrogen@notyetimplemented.com> X-Archives-Salt: 84bd0c76-bda4-4e07-bb61-847371c8b97a X-Archives-Hash: 773b34984a857e3af2d51457650dac63 On Sunday 06 May 2007 2:21:02 pm Ciaran McCreesh wrote: > On Sun, 6 May 2007 14:17:29 -0400 > > Dan Meltzer wrote: > > > > which elog could easily be extended to do. > > > > > > But which elog does not do by default, and for good reason. > > > > and what good reason would that be? > > That elog is designed for post-install messages that aren't necessarily > relevant to many users. No, its designed to save messages for users to read. It was implemented because important information scrolled off the screen in major updates. If a user chooses not to read warn level messages from elog then they are responsible for the breakage, why abuse news for it? -- gentoo-dev@gentoo.org mailing list