From: Craig Rodrigues <rodrigc@mediaone.net>
To: Jason Molenda <jason-gcclist@molenda.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GNATS Login
Date: Mon, 17 Dec 2001 08:35:00 -0000 [thread overview]
Message-ID: <20011217110511.A22669@mediaone.net> (raw)
In-Reply-To: <20011216231958.A72266@molenda.com>; from jason-gcclist@molenda.com on Sun, Dec 16, 2001 at 11:19:58PM -0800
On Sun, Dec 16, 2001 at 11:19:58PM -0800, Jason Molenda wrote:
>
> gnats will be undergoing a big change when gnats v4 is finished;
> it will probably be worthwhile to upgrade to that on gcc.gnu.org
> at some point, and they may have addressed this issue in gnats v4
> in a more integrated manner.
There was some talk at looking at bugzilla, due to the
shortcomings in GNATS:
http://gcc.gnu.org/ml/gcc/2001-11/msg00870.html
Is there still interest in this? As a heavy user
of GCC GNATS, I find that the lack of good support
for mime attachments makes it inconvenient to use,
especially when a bug submitter submits 5000 lines
of preprocessed source in a web text entry field.
I might be able to spend some time looking at GNATS
sometime in the beginning of 2002.
--
Craig Rodrigues
http://www.gis.net/~craigr
rodrigc@mediaone.net
next prev parent reply other threads:[~2001-12-17 16:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 23:33 Linux Kernel, KDE & GCC 3.0.3 Adam Schrotenboer
2001-12-14 7:57 ` Craig Rodrigues
2001-12-14 9:12 ` Franz Sirl
2001-12-14 18:31 ` GNATS Login was " Adam Schrotenboer
2001-12-14 22:56 ` Craig Rodrigues
2001-12-15 4:30 ` Gerald Pfeifer
2001-12-15 2:00 ` Andreas Jaeger
2001-12-16 23:09 ` GNATS Login Jason Molenda
2001-12-16 23:16 ` Craig Rodrigues
2001-12-16 23:28 ` Jason Molenda
2001-12-17 8:35 ` Craig Rodrigues [this message]
2001-12-21 1:08 ` Gerald Pfeifer
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=20011217110511.A22669@mediaone.net \
--to=rodrigc@mediaone.net \
--cc=gcc@gcc.gnu.org \
--cc=jason-gcclist@molenda.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).