public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.demon.co.uk>
To: Craig Rodrigues <rodrigc@mediaone.net>
Cc: gcc@gcc.gnu.org
Subject: Re: Using GNATS to track GCC patches
Date: Mon, 05 Nov 2001 10:53:00 -0000	[thread overview]
Message-ID: <20011117181230.B9631@daikokuya.demon.co.uk> (raw)
In-Reply-To: <20011117104102.A14701@mediaone.net>

Craig Rodrigues wrote:-

> I recall from the following thread that the idea
> of using GNATS to track patches in GCC came up:
> 
> http://gcc.gnu.org/ml/gcc/2000-06/msg00264.html
> http://gcc.gnu.org/ml/gcc/2000-06/msg00263.html
> 
> Has anyone made any move to implement this?

It might be a good idea, but I don't think that enough people take
GNATS seriously.  Only 4 or 5 of us use it regularly, and I think it's
fair to say that everyone with global write privs hardly uses it at
all.  Mark and rth seem to be the only ones that do, and only then
very occasionally.

So, I don't think this is a good idea at present, since it would just
clutter up GNATS.

I also feel that GNATS is a bit, um, flimsy and breaks easily, and is
not heavy-duty enough for what we'd really like.  We realy want proper
bug cross-referencing, cross-dependency tracking, a proper idea of
duplicates, etc, etc. much like Bugzilla does and GNATS doesn't appear
to do at all.

Neil.

  reply	other threads:[~2001-11-17 18:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-05  9:58 Craig Rodrigues
2001-11-05 10:53 ` Neil Booth [this message]
2001-11-06 19:29   ` Gerald Pfeifer
2001-11-06 20:06     ` Joseph S. Myers
2001-11-07  4:08   ` Jakub Jelinek
2001-11-07  4:17     ` Joseph S. Myers
2001-11-07  7:14       ` Bryce McKinlay
     [not found]         ` <3BF8CF07.E8ECFC3F@acter.ch>
     [not found]           ` <3BF8D467.9010605@waitaki.otago.ac.nz>
2001-11-07  8:16             ` Adrian von Bidder
2001-11-08  7:31               ` Phil Edwards
2001-11-08  7:14         ` Phil Edwards

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=20011117181230.B9631@daikokuya.demon.co.uk \
    --to=neil@daikokuya.demon.co.uk \
    --cc=gcc@gcc.gnu.org \
    --cc=rodrigc@mediaone.net \
    /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).