public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Reporting GCC bugs
Date: Thu, 11 Oct 2012 16:28:00 -0000	[thread overview]
Message-ID: <CAKOQZ8znfNMFEiN0XwQSQQNMie2wXojijB9jZ3f-GQJntYOa3A@mail.gmail.com> (raw)
In-Reply-To: <87mwztvyw0.fsf@gnu.org>

On Thu, Oct 11, 2012 at 7:58 AM, Ludovic Courtès <ludo@gnu.org> wrote:
>
> Ian Lance Taylor <iant@google.com> skribis:
>
>> Requiring an account with a valid e-mail address is
>> an unfortunate necessity on the current Internet,
>
> Several GNU projects have been using Debbugs at <http://bugs.gnu.org/>
> for some time.  It doesn’t require subscription.
>
> I’ve never seen any spam there, perhaps thanks to Savannah’s shared spam
> filters.  More importantly, it’s very convenient for most
> hackers–there’s even a pleasant Emacs mode to browse bugs.

At first glance, it looks to be a fairly different kind of system: it
looks like you can only report bugs by e-mail.  GCC used to use a
system like that: GNATS.  Bugzilla is working quite a bit better for
GCC.

Not that I'm opposed to changing if people really think it would be better.

Ian

  reply	other threads:[~2012-10-11 16:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09 14:53 Torbjorn Granlund
2012-10-09 16:08 ` Ian Lance Taylor
2012-10-09 16:40   ` Torbjorn Granlund
2012-10-09 18:23     ` Paul Smith
2012-10-10 15:54     ` Ian Lance Taylor
2012-10-11 14:59   ` Ludovic Courtès
2012-10-11 16:28     ` Ian Lance Taylor [this message]
     [not found]   ` <CAF1jjLsRRWLQm_vfdzSDBVVFc_-UG0=v17PTFbZcnjcBD-x4wQ@mail.gmail.com>
     [not found]     ` <CAKOQZ8zOxNiPSpsPh0DUAw_JuLehkoeAza968bzD1qPuoMJ7bg@mail.gmail.com>
     [not found]       ` <CAH6eHdTN=KxUB8VQUg9S1myzJU4CthoLSSgTXMr-Cz6R+aj0sg@mail.gmail.com>
2012-11-02 14:32         ` Ángel González
2012-11-30  5:33           ` NightStrike
2012-11-30  5:37             ` Ian Lance Taylor
2012-11-30 12:23               ` Frédéric Buclin
2012-11-30 12:35                 ` NightStrike

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=CAKOQZ8znfNMFEiN0XwQSQQNMie2wXojijB9jZ3f-GQJntYOa3A@mail.gmail.com \
    --to=iant@google.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=ludo@gnu.org \
    /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).