From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: dberlin@dberlin.org, mec.gnu@mindspring.com
Cc: cagney@gnu.org, cgf@alum.bu.edu, gdb@sources.redhat.com
Subject: Re: bugzilla
Date: Thu, 08 Jul 2004 19:44:00 -0000 [thread overview]
Message-ID: <20040708194348.6067E4B104@berman.michael-chastain.com> (raw)
> So if you guys want new fields, they need to be all decided before the
> merge, so i can add all the necessary display stuff, etc :).
Fair enough.
Here is my list of fields. I started with the gcc bugzilla list:
Reporter
Product
Version
Component
Priority
Severity
Assigned To
CC
Host Triplet
Target Triplet
Build Triplet
Summary
Description
The additional fields I want are:
Target Operating System Version
(such as red hat linux 8, etc)
Compiler Name
(gcc, hp ansi c, hp acc, various sun compilers, diab, etc)
Compiler Version
(The compiler that you built your program with,
not the compiler that you built gcc with.
If gdb successfully builds, then gdb works the same no
matter what compiler you build it with. However, gdb
reads debug information from your program, so we need
the name and version of the compiler which you used to
compile your program)
Debug Format
(dwarf-2, stabs+, som, mdebug, ..., other)
mec> . collapse 'priority' and 'severity' into one field,
mec> or actually document what they mean in the online help.
db> I can't do this if you use the sources bugzilla installation, since
db> they use priority and severity.
This is low priority to me. I can live with whatever is easiest for
you, including no changes at all.
Michael C
next reply other threads:[~2004-07-08 19:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 19:44 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-14 0:56 Bugzilla Nick Roberts
2009-10-15 9:42 ` Bugzilla Doug Evans
2009-10-15 16:07 ` Bugzilla Tom Tromey
2009-10-17 1:05 ` Bugzilla Nick Roberts
2009-10-17 9:39 ` Bugzilla Tom Tromey
2009-10-18 1:03 ` Bugzilla Daniel Jacobowitz
2009-10-18 2:27 ` Bugzilla Nick Roberts
2009-10-18 2:46 ` Bugzilla Daniel Jacobowitz
2009-10-18 19:41 ` Bugzilla Joel Brobecker
2009-10-20 7:56 ` Bugzilla Nick Roberts
2009-10-20 10:02 ` Bugzilla Joel Brobecker
2007-03-21 8:00 Bugzilla Sascha Radike
2007-03-21 11:11 ` Bugzilla Daniel Jacobowitz
2007-03-21 11:29 ` Bugzilla Sascha Radike
2007-03-21 11:45 ` Bugzilla 'Daniel Jacobowitz'
2004-07-08 18:07 bugzilla Michael Elizabeth Chastain
2004-07-08 18:03 bugzilla Michael Elizabeth Chastain
2004-07-08 19:17 ` bugzilla Daniel Berlin
2004-07-08 14:31 bugzilla Andrew Cagney
2004-07-08 14:52 ` bugzilla Daniel Berlin
2004-07-08 15:07 ` bugzilla Andrew Cagney
2004-07-08 15:11 ` bugzilla Daniel Jacobowitz
2004-07-08 15:17 ` bugzilla Daniel Berlin
2004-07-08 15:16 ` bugzilla Daniel Berlin
2004-07-08 14:59 ` bugzilla Dave Korn
2004-07-08 15:15 ` bugzilla Daniel Berlin
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=20040708194348.6067E4B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=cgf@alum.bu.edu \
--cc=dberlin@dberlin.org \
--cc=gdb@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