From: Owen Gunden <ogunden@stwing.upenn.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] patch: emergemail feature in functions.sh
Date: Tue, 19 Aug 2003 19:53:39 -0400 [thread overview]
Message-ID: <20030819235338.GB5978@force.stwing.upenn.edu> (raw)
In-Reply-To: <200308190850.43935.kaschu@t800.ping.de>
On Tue, Aug 19, 2003 at 08:50:43AM +0200, Karsten Schulz wrote:
> what about collection all einfo/ewarn/eerror output in an ENV variable
> (or in a temporary file) and send them in one mail to root after each
> stage of the emerge process (compile, install, ...)?
I took Karsten's advice and produced a new patch which doesn't have the
major limitation of my last one. I've used it with a couple emerges
already and I'm totally hooked :). See [1] for discussion and the patch.
Owen
References:
1. http://bugs.gentoo.org/show_bug.cgi?id=11359
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-19 23:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 5:37 [gentoo-dev] patch: emergemail feature in functions.sh Owen Gunden
2003-08-19 5:44 ` Jon Portnoy
2003-08-19 5:54 ` Mike Frysinger
2003-08-19 6:50 ` Karsten Schulz
2003-08-19 8:34 ` Owen Gunden
2003-08-19 23:53 ` Owen Gunden [this message]
2003-08-19 13:05 ` Thomas de Grenier de Latour
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=20030819235338.GB5978@force.stwing.upenn.edu \
--to=ogunden@stwing.upenn.edu \
--cc=gentoo-dev@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