public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Christopher Faylor <cgf@redhat.com>
Cc: Daniel Berlin <dberlin@dberlin.org>,  <overseers@gcc.gnu.org>
Subject: Re: Web part of bugzilla is ready (fwd)
Date: Sat, 08 Feb 2003 12:39:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0302081234001.366-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <20030208024436.GA27397@redhat.com>

On Fri, 7 Feb 2003, Christopher Faylor wrote:

> On the other side, I think that anything that shows up in bugzilla should
> generate gcc-bugs email.  There's no reason to generate gcc-prs mail,
> AFAICT.  You can do that now with no help from me, I think.

I believe that the gcc-bugs list should be told that gcc-bugzilla (or 
whatever - the Bugzilla address that mail followups to Bugzilla bugs get 
sent to) is another name for itself, so it accepts messages without 
gcc-bugs explicitly in their headers.  (A followup mail sent to 
gcc-bugzilla should appear on the list and in the database.  If people CC 
mails to both this means lots of messages get duplicated on the list, 
which is undesirable, so it's good if the messages on gcc-bugs don't 
actually mention gcc-bugs in the To/CC headers if they mention 
gcc-bugzilla.  This can always be dealt with after the transition if 
complicated; duplicate messages aren't too serious a problem.  The gcc-prs 
list can then go away - the only messages it gets that gcc-bugs doesn't 
are mail followups to PRs sent to gcc-gnats only, and they should appear 
on gcc-bugs in future.)

-- 
Joseph S. Myers
jsm28@cam.ac.uk

      parent reply	other threads:[~2003-02-08 12:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04  4:17 Daniel Berlin
2003-02-04  4:36 ` Christopher Faylor
2003-02-05  8:04   ` Jason Molenda
2003-02-06  0:31     ` Daniel Berlin
2003-02-08  2:45       ` Christopher Faylor
2003-02-08  4:53         ` Daniel Berlin
2003-02-08 16:25           ` Christopher Faylor
2003-02-08 16:36             ` Christopher Faylor
2003-02-08 17:06               ` Daniel Berlin
2003-02-10  1:23             ` Daniel Berlin
2003-02-21  1:13               ` Christopher Faylor
2003-02-08 12:39         ` Joseph S. Myers [this message]

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=Pine.LNX.4.33.0302081234001.366-100000@kern.srcf.societies.cam.ac.uk \
    --to=jsm28@cam.ac.uk \
    --cc=cgf@redhat.com \
    --cc=dberlin@dberlin.org \
    --cc=overseers@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).