On Mon, 8 Jan 2007 21:01:07 +0100 Thilo Bangert <[EMAIL PROTECTED]> wrote:
> Hi, > > Marius Mauch <[EMAIL PROTECTED]> said: > > Basically if it's for the user to read use elog, if it's just a > > status message (like "applying patch", "nothing to do here", > > "performing xyz") that isn't of any use after the build use einfo. > > > > and what about ewarn? Order of importance: einfo < elog < ewarn < eerror (this is consistent with syslog). > > > will einfo reporting to the elog framework be turned off in the > > > future? > > > > No. However einfo logging is not enabled by default, > > IMHO it should be. No. einfo is (now) supposed to be disposable. If a user wants it, it's trivial to enable, but all significant messages should use elog or higher. Marius -- [email protected] mailing list
