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
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?
> > will einfo reporting to the
On Sun, 7 Jan 2007 17:26:12 +0100
Thilo Bangert <[EMAIL PROTECTED]> wrote:
> Marius Mauch <[EMAIL PROTECTED]> said:
> > Just a heads up that in the coming weeks I'll start checking
> > packages that still use einfo for important messages and convert
> > them to elog if appropriate.
>
> whats the
On Sunday 07 January 2007 11:26, Thilo Bangert wrote:
> Marius Mauch <[EMAIL PROTECTED]> said:
> > Just a heads up that in the coming weeks I'll start checking packages
> > that still use einfo for important messages and convert them to elog if
> > appropriate.
>
> whats the policy? when do i use e
Marius Mauch <[EMAIL PROTECTED]> said:
> Just a heads up that in the coming weeks I'll start checking packages
> that still use einfo for important messages and convert them to elog if
> appropriate.
whats the policy? when do i use einfo and when elog?
the dev handbook states for einfo:
In
Just a heads up that in the coming weeks I'll start checking packages
that still use einfo for important messages and convert them to elog if
appropriate. If you have a problem with me doing that for your
packages that notify me off-list.
You can find the current list of packages to check at
dev.ge
