From: Eric McDonald <emcdonal@cps.cmich.edu>
To: Jim Kingdon <kingdon@panix.com>
Cc: xconq7@sources.redhat.com
Subject: Re: xconq gnatsweb
Date: Tue, 17 Jun 2003 17:06:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.53.0306171256080.2752@cps201.cps.cmich.edu> (raw)
In-Reply-To: <200306171455.h5HEtcU11307@panix5.panix.com>
On Tue, 17 Jun 2003, Jim Kingdon wrote:
> I looked at bug 4 and it seems to already be fixed. But I don't know
> how to log in to gnats. The whole thing seems to be rather less easy
> to use than bugzilla...
I think the gcc people switched over to bugzilla a while ago, and for a fairly
large open source community like that to make the switch, bugzilla must have
some merit over the others....
If no one is planning on maintaining a defect tracking system, then I suppose we
should submit PR's to the list?
next prev parent reply other threads:[~2003-06-17 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 14:55 Eric McDonald
2003-06-17 15:11 ` Jim Kingdon
2003-06-17 17:06 ` Eric McDonald [this message]
2003-06-17 17:11 ` Hans Ronne
2003-06-18 20:57 ` Erik Jessen
[not found] ` <l03130300bb21b792b545@[212.181.162.155]>
[not found] ` <l03130300bb231fa06240@[212.181.162.155]>
[not found] ` <l03130300bb25284b2a32@[212.181.162.155]>
[not found] ` <l03130300bb256ec7be1d@[212.181.162.155]>
[not found] ` <l03130300bb26099427db@[212.181.162.155]>
2003-07-01 7:39 ` Table: can-enter-independent Eric McDonald
[not found] <l03130300bb2594c3ad59@[212.181.162.155]>
[not found] ` <l03130301bb212d8a3de0@[212.181.162.155]>
[not found] ` <l03130300bb20f68830c2@[212.181.162.155]>
[not found] ` <l03130300bb16b78c511e@[212.181.162.155]>
[not found] ` <l03130300bb162bac418e@[212.181.162.155]>
[not found] ` <l03130300bb159901c29c@[212.181.162.155]>
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.GSO.4.53.0306171256080.2752@cps201.cps.cmich.edu \
--to=emcdonal@cps.cmich.edu \
--cc=kingdon@panix.com \
--cc=xconq7@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).