public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Milan Zamazal <pdm@zamazal.org>
To: Bryce McKinlay <bryce@albatross.co.nz>
Cc: gnats-devel@sources.redhat.com, gcc@gcc.gnu.org
Subject: Re: GNATS feature requests
Date: Sun, 08 Apr 2001 11:28:00 -0000	[thread overview]
Message-ID: <87n19rbdx7.fsf@zamazal.org> (raw)
In-Reply-To: <3AA80A54.4BEFCBE8@albatross.co.nz>

>>>>> "BM" == Bryce McKinlay <bryce@albatross.co.nz> writes:

    BM> Here are a few requests for GNATS features that would fix
    BM> problems with the GCC bug database which I find annoying...

    BM> 1. Ability to notify multiple mailing lists of follow-ups to
    BM> certain PR categories.

[...]

    BM> 2. Notification of changes to fields like "synopsis" and
    BM> "class-id".

[...]

    BM> 3. If I mark a bug as a duplicate, it would be really helpful if
    BM> GNATS would add the email of the originator of the duplicate PR
    BM> to the notification/contact list of the original/canonical PR

[...]

I think all the requests are reasonable.  I'll try to implement once
GNATS 4 is released (till that time, there are more critical tasks like
getting the system work well, to fix all important bugs from BTS, and
updating the manual).

Regards,

Milan Zamazal

-- 
I think any law that restricts independent use of brainpower is suspect.
                                               -- Kent Pitman in comp.lang.lisp

  reply	other threads:[~2001-04-08 11:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-08 14:31 Bryce McKinlay
2001-04-08 11:28 ` Milan Zamazal [this message]
2001-04-09  2:22   ` Richard Earnshaw
2001-04-09 12:12     ` Milan Zamazal
2001-04-09  3:27   ` Bryce McKinlay

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=87n19rbdx7.fsf@zamazal.org \
    --to=pdm@zamazal.org \
    --cc=bryce@albatross.co.nz \
    --cc=gcc@gcc.gnu.org \
    --cc=gnats-devel@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).