public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: DJ Delorie <dj@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: A few suggestions for bugzilla mail to gcc-bugs
Date: Sat, 24 May 2003 03:57:00 -0000	[thread overview]
Message-ID: <CF4B91CF-8D9A-11D7-AC8F-000A95A34564@dberlin.org> (raw)
In-Reply-To: <200305240305.h4O350922816@greed.delorie.com>


On Friday, May 23, 2003, at 11:05  PM, DJ Delorie wrote:

>
>> Yes, but i can't automate people doing the right thing.
>
> How about a procmail rule?

Funny you mention, when i sugggested a procmail rule to chris for 
handling mail to gcc-gnats, so that i didn't have to handle it in the 
script, he said handling it in the script would be much easier than 
trying to get qmail to run procmail and do this, etc.

>  If gcc-bugs gets mail and sees
> To:.*gcc-bugzilla in the headers, it silently discards the email.
>
> Assuming gcc-bugs uses procmail, of course.
>

It doesn't, it uses qmail + something else.

--Dan

  reply	other threads:[~2003-05-24  3:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-24  2:02 Segher Boessenkool
2003-05-24  2:14 ` Daniel Berlin
2003-05-24  2:56   ` Daniel Jacobowitz
2003-05-24  3:05     ` Daniel Berlin
2003-05-24  3:09       ` DJ Delorie
2003-05-24  3:57         ` Daniel Berlin [this message]
2003-05-24 15:15       ` Daniel Jacobowitz
2003-06-02 20:02         ` Andreas Schwab
2003-06-02 21:34           ` Daniel Berlin
2003-06-02 21:38             ` Daniel Jacobowitz
2003-06-02 21:54               ` Daniel Berlin
2003-06-02 22:03                 ` Daniel Jacobowitz
2003-05-24  3:42     ` Segher Boessenkool
2003-05-24  9:52   ` Joseph S. Myers
2003-05-24 15:46     ` Daniel Berlin
2003-05-24 20:17       ` Joseph S. Myers

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=CF4B91CF-8D9A-11D7-AC8F-000A95A34564@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=dj@redhat.com \
    --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).