From: Thomas de Grenier de Latour <degrenier@easyconnect.fr>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] a suggestion about einfo messages
Date: Wed, 21 Jul 2004 18:01:15 +0200 [thread overview]
Message-ID: <20040721180115.0fda0191@eusebe> (raw)
In-Reply-To: <43241.66.99.246.226.1090423772.squirrel@66.99.246.226>
On Wed, 21 Jul 2004 10:29:32 -0500 (CDT)
"Joseph Booker" <joe@neoturbine.net> wrote:
> I think what he was saying, is that einfo (and i guess ewarn
> also) would be redirected to a file, what about the same file as
> the regular PORT_LOGDIR, but with *.einfos.log files also? (or
> instead of?)
That was one of the features of my "really quiet mode for emerge"
patchset, that you can still find here :
http://bugs.gentoo.org/show_bug.cgi?id=37491
I've stopped updating this patch after portage-2.0.50-r1, by
lack of time and feedback. But if you look at the ebuild.sh part
of the patch, you will find some piece of code that can help
implementing this idea.
--
TGL.
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-07-21 16:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 8:22 [gentoo-portage-dev] a suggestion about einfo messages YiDa Chiang
2004-07-21 9:04 ` Michael Kohl
2004-07-21 15:29 ` Joseph Booker
2004-07-21 15:51 ` Michael Kohl
2004-07-21 16:15 ` Thomas de Grenier de Latour
2004-07-21 16:19 ` Michael Kohl
2004-07-21 16:01 ` Thomas de Grenier de Latour [this message]
2004-07-21 16:06 ` Joseph Booker
2004-07-21 21:30 ` [gentoo-portage-dev] " Joel Konkle-Parker
2004-07-22 20:48 ` Joseph Booker
2004-07-22 21:31 ` Joel Konkle-Parker
2004-07-23 9:08 ` Kumba
2004-07-23 11:32 ` Joel Konkle-Parker
2004-07-25 15:57 ` [gentoo-portage-dev] SSE2 and MMX2 use flags Roman Gaufman
2004-07-25 16:16 ` Marius Mauch
2004-07-25 18:06 ` Roman Gaufman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040721180115.0fda0191@eusebe \
--to=degrenier@easyconnect.fr \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox