From: Daniel Berlin <dberlin@dberlin.org>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Bugzilla sanity check errors. :-)
Date: Fri, 23 May 2003 21:17:00 -0000 [thread overview]
Message-ID: <FBB93D5F-8D60-11D7-AC8F-000A95A34564@dberlin.org> (raw)
In-Reply-To: <20030523161939.GA2235@doctormoo>
On Friday, May 23, 2003, at 12:19 PM, Nathanael Nerode wrote:
> Daniel Berlin said:
>
>> No, i'll take care of it.
>> If it makes any of you feel better about getting spammed on gcc-bugs,
>> realize i get copies of all mail failures (since there is no
>> unassigned@gcc.gnu.org, that's at least one for every change to an
>> unassigned bug).
>
> Good GOD. How do you MANAGE?
It all gets thrown in a separate mailbox, which i look at a few times a
day to make sure nothing really bad is going on.
I'm 23 (24 on June 9th), so i'm young still and have lots of energy,
unlike all you old geezers.
:)
--Dan
>
> --Nathanael
next prev parent reply other threads:[~2003-05-23 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 16:53 Nathanael Nerode
2003-05-23 21:17 ` Daniel Berlin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-23 6:40 Nathanael Nerode
2003-05-23 14:35 ` Daniel Berlin
2003-05-23 15:50 ` Nathanael Nerode
2003-05-23 16:19 ` Daniel Berlin
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=FBB93D5F-8D60-11D7-AC8F-000A95A34564@dberlin.org \
--to=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=neroden@twcny.rr.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).