From: Daniel Berlin <dberlin@dberlin.org>
To: gcc@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: Please test the gcc bugzilla interface
Date: Sun, 23 Feb 2003 04:37:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.50.0302221933130.32564-100000@dberlin.org> (raw)
The gcc bugzilla email interface needs testing.
Send a message with a subject of "help" to gcc-bugzilla@sources.redhat.com
to get usage instructions (somewhat incomplete).
It doesn't allow you to *report* new bugs by mail (that's a different
script not on this alias right now), only get copies of, or modify
(close, retitle, reassign, etc), existing ones.
Appending comments to existing bug reports (like what happens if you send
a followup to a bug email) is also a different script that's not on this
alias right now (When it is set up, it'll work like it does now)
Feel free to also let me know what enhancements you guys want to it that
are reasonable, and *would actually be used*.
For instance, right now, it can send you lists of bugs for a given
product/component (or product/all components), but not for a given
product/version or component/version.
I'll get to this eventually.
Obviously, you can do much more in terms of queries with the
bugzilla web interfaces, and i don't ever expect or want to completely
duplicate the functionality of the web interface with an email interface.
Just make it convenient for developers to do things by email
when they want to, rather than having to fire up a web browser
just to close a bug.
Note that if you don't have a bugzilla account, it will make one for you.
If you've ever submitted or replied to or have your name *somewhere* in a
gcc gnats database, you have a bugzilla account automatically, and thus,
it won't create another one for you.
Any error emails that are pertinent should be forwarded to me so i can fix
the problems.
The bug database is currently a week or two behind the gnats one, in
case it tells you a bug doesn't exist that you think does.
--Dan
reply other threads:[~2003-02-23 2:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.50.0302221933130.32564-100000@dberlin.org \
--to=dberlin@dberlin.org \
--cc=gcc-patches@gcc.gnu.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).