public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Tim Prince <timothyprince@sbcglobal.net>
To: Wolfgang Bangerth <bangerth@ices.utexas.edu>,
Dara Hazeghi <dhazeghi@yahoo.com>
Cc: <gcc-bugs@gcc.gnu.org>
Subject: Re: NEW vs. UNCONFIRMED
Date: Sun, 01 Jun 2003 03:56:00 -0000 [thread overview]
Message-ID: <200306010356.h513ui3T033980@pimout2-ext.prodigy.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0305312002550.10118-100000@gandalf.ices.utexas.edu>
On Saturday 31 May 2003 18:15, Wolfgang Bangerth wrote:
> > Finally, a question about maintainers and bugs. Is there a consensus as
> > to when it is okay to assign a bug to someone, and when it is okay to
> > add someone (who's responsible for the relevant portion of the
> > compiler) to the cc: list of a bug? Thanks,
>
I've been put on the CC: list for all bugs, according to the bugzilla
messages. If this happened for many people, no wonder your server gets
behind.
--
Tim Prince
next prev parent reply other threads:[~2003-06-01 3:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <486DCCCA-93CC-11D7-A14F-000393681B36@yahoo.com>
2003-06-01 1:15 ` Wolfgang Bangerth
2003-06-01 1:32 ` Andrew Pinski
2003-06-01 1:38 ` Wolfgang Bangerth
2003-06-01 3:56 ` Tim Prince [this message]
2003-06-01 4:25 Dara Hazeghi
-- strict thread matches above, loose matches on Subject: below --
2003-06-01 4:21 Dara Hazeghi
2003-06-02 15:53 ` Wolfgang Bangerth
2003-06-01 1:01 Dara Hazeghi
2003-06-02 7:32 ` Ben Elliston
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=200306010356.h513ui3T033980@pimout2-ext.prodigy.net \
--to=timothyprince@sbcglobal.net \
--cc=bangerth@ices.utexas.edu \
--cc=dhazeghi@yahoo.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=tprince@computer.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).