public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: gcc@gcc.gnu.org
Subject: At the request of those drowing in gcc-bugs email
Date: Wed, 21 May 2003 21:07:00 -0000	[thread overview]
Message-ID: <2645E0FC-8BD0-11D7-AF07-000A95A34564@dberlin.org> (raw)

I have changed gcc-bugs's email preferences so it only gets mail about 
the following:

"New Comments are added"
"Priority, status, severity, and/or milestone changes"
"The bug is resolved or verified "
"The bug is in the unconfirmed state"

The following will not cause gcc-bugs to receive mail:
"New Attachments are added"
"Keywords field changes"
"CC field changes"
"Any field not mentioned above changes"


If we want to make decisions that we want certain types of mail to go 
to certain lists or something, we can.

--Dan

             reply	other threads:[~2003-05-21 21:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-21 21:07 Daniel Berlin [this message]
2003-05-21 21:12 ` H. J. Lu
2003-05-21 21:21   ` Daniel Berlin
2003-05-21 21:25 ` Joseph S. Myers
2003-05-21 21:37   ` Daniel Berlin
2003-05-21 21:28 ` Christian Ehrhardt
2003-05-21 21:44 Wolfgang Bangerth
2003-05-21 21:49 ` Daniel Berlin
2003-05-21 22:28   ` Wolfgang Bangerth

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=2645E0FC-8BD0-11D7-AF07-000A95A34564@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=gcc@gcc.gnu.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).