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 1Hkmyq-0001zf-IZ for garchives@archives.gentoo.org; Sun, 06 May 2007 20:05:17 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l46K4BpP017490; Sun, 6 May 2007 20:04:11 GMT Received: from randymail-a9.g.dreamhost.com (sd-green-bigip-81.dreamhost.com [208.97.132.81]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l46K0tFd012729 for ; Sun, 6 May 2007 20:00:55 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 7FB44EF088 for ; Sun, 6 May 2007 13:00:55 -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 16:00:56 -0400 User-Agent: KMail/1.9.6 References: <1178433936.13701.10.camel@ip6-localhost> <200705061543.45529.hydrogen@notyetimplemented.com> <20070506205347.1e4e8801@snowflake> In-Reply-To: <20070506205347.1e4e8801@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: <200705061600.56357.hydrogen@notyetimplemented.com> X-Archives-Salt: d470c2fd-691f-417a-b02c-0c0474425e08 X-Archives-Hash: 6b82e5f4175e098d1f7f9999bb92e3ca On Sunday 06 May 2007 3:53:47 pm Ciaran McCreesh wrote: > On Sun, 6 May 2007 15:43:45 -0400 > > Dan Meltzer wrote: > > No, I've read the other threads. You've not explained how this is a > > critical update that requires a news item. You've said repeatedly in > > response to related questions that your experience with news for one > > package in one overlay used by a small subset of users that uses said > > package recieved good feedback, and that they would like to be > > informed of changes in the future. You were informed that elog can do > > just that, and you said repeatedly that elog is not sufficient > > because its not loggged by default. You could easily make elog > > logged by default in paludis, and that would achieve the same result > > as a news item. What did I forget? > > Er, making elog logged by default would not solve the "requires an > explicit read" problem. Making elog require an explicit read would > be far too annoying because most elog notices are noise. We've been > over this already. Not if one filters it properly. ELOG_CLASSES="warn error" sounds like a sane default to me. -- gentoo-dev@gentoo.org mailing list