From: Daniel Berlin <dberlin@dberlin.org>
To: Christopher Faylor <cgf@redhat.com>
Cc: overseers@sources.redhat.com
Subject: Re: creating two new email aliases
Date: Sun, 08 Feb 2004 17:02:00 -0000 [thread overview]
Message-ID: <7FD15370-5A58-11D8-B8AA-000A95DA505C@dberlin.org> (raw)
In-Reply-To: <20040208165635.GC1855@redhat.com>
On Feb 8, 2004, at 11:56 AM, Christopher Faylor wrote:
> On Sun, Feb 08, 2004 at 09:08:51AM -0500, Ian Lance Taylor wrote:
>> Daniel Berlin <dberlin@dberlin.org> writes:
>>> unassigned@gcc.gnu.org and unassigned@sources.redhat.com
>>>
>>> They should both just go to /dev/null (ie accept and discard).
>>
>> Done.
>
> Wait. Why do we need these again? Why isn't bugzilla smart enough to
> *not send email* to unassigned?
unassigned is a real user, and the default owner of bugs.
(It's a holdover from the gnats database).
prev parent reply other threads:[~2004-02-08 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 4:57 Daniel Berlin
2004-02-08 14:08 ` Ian Lance Taylor
2004-02-08 16:56 ` Christopher Faylor
2004-02-08 17:02 ` Daniel Berlin [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=7FD15370-5A58-11D8-B8AA-000A95DA505C@dberlin.org \
--to=dberlin@dberlin.org \
--cc=cgf@redhat.com \
--cc=overseers@sources.redhat.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).