From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: dberlin@dberlin.org, <gcc@gcc.gnu.org>
Subject: Re: At the request of those drowing in gcc-bugs email
Date: Wed, 21 May 2003 21:44:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0305211639250.2189-100000@gandalf.ices.utexas.edu> (raw)
>> I have another request about the messages that Bugzilla generates: could
>> they have the name of the person responsible for the new bug, comment,
>> etc., in the From header (keeping the gcc-bugzilla address there as the
>> email address, though From can contain multiple addresses) so it's visible
>> on the list who is commenting on bugs?
>
> It's already *in* the actual text, but i'll look into it.
> It might take me a day or so to get it done.
Yes, I would really like this too. We recently had a number of people
coming into the project and when we decided we wanted to give them GNATS
write access, I kept an eye on what they did for a while. That's
impossible if the name of the one changing something in the database
doesn't appear in the From: header. (I.e.: it _is_ possible, but I would
again have to look at all mails, which I don't want and can't).
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ices.utexas.edu
www: http://www.ices.utexas.edu/~bangerth/
next reply other threads:[~2003-05-21 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 21:44 Wolfgang Bangerth [this message]
2003-05-21 21:49 ` Daniel Berlin
2003-05-21 22:28 ` Wolfgang Bangerth
-- strict thread matches above, loose matches on Subject: below --
2003-05-21 21:07 Daniel Berlin
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
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.44.0305211639250.2189-100000@gandalf.ices.utexas.edu \
--to=bangerth@ices.utexas.edu \
--cc=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).