On Sunday 06 May 2007 3:53:47 pm Ciaran McCreesh wrote: > On Sun, 6 May 2007 15:43:45 -0400 > > Dan Meltzer <[EMAIL PROTECTED]> 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. -- [EMAIL PROTECTED] mailing list
