From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: mrs@windriver.com
Cc: gcc@gcc.gnu.org
Subject: Re: Removing GNATS categories
Date: Tue, 28 Mar 2000 14:33:00 -0000 [thread overview]
Message-ID: <200003282230.AAA01046@loewis.home.cs.tu-berlin.de> (raw)
In-Reply-To: <200003282024.MAA09770@kankakee.wrs.com>
> But, you see, there are experts that can recategorize into finer
> detail. I know that I have always wanted, and often used finer
> resolution than just g++. EH/pt/mi/rtti/vtbl and so on... I find
> such micro categories very useful. It'd be nice for gnats to support
> a subcategory, then the main one could be g++, with the minor one be
> even more specific.
I agree. What we probably could do is to add the categories, and not
expose them to the submitter. Not adding them into the gccbug script
is easy. Not adding them in gnatsweb.pl is more difficult, unless we
have two cgi scripts - one for database maintainers, and one for
submitters. Again, this is a request for perl hackers - any
volunteers?
Otherwise, I guess I just have to rewrite gnatsweb in Python - is
there a Python installation on sourceware? :-)
Regards,
Martin
next prev parent reply other threads:[~2000-03-28 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-28 12:25 Mike Stump
2000-03-28 14:33 ` Martin v. Loewis [this message]
2000-03-29 3:59 ` Branko
2000-03-29 11:31 ` Martin v. Loewis
2000-03-29 22:46 ` Branko
2000-03-30 5:17 ` Branko
-- strict thread matches above, loose matches on Subject: below --
2000-03-28 1:49 Martin v. Loewis
2000-03-28 7:03 ` Jeffrey A Law
2000-03-29 12:21 ` Martin v. Loewis
2000-03-29 12:55 ` Tom Tromey
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=200003282230.AAA01046@loewis.home.cs.tu-berlin.de \
--to=martin@loewis.home.cs.tu-berlin.de \
--cc=gcc@gcc.gnu.org \
--cc=mrs@windriver.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).