From: Christopher Faylor <cgf@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb@sources.redhat.com
Subject: Re: gcc HEAD bad stabs (?)
Date: Sat, 13 Sep 2003 00:36:00 -0000 [thread overview]
Message-ID: <20030913003648.GD26022@redhat.com> (raw)
In-Reply-To: <200309130017.h8D0HgJl028923@duracef.shout.net>
On Fri, Sep 12, 2003 at 08:17:42PM -0400, Michael Elizabeth Chastain wrote:
>cgf> Hmm. Have you considered sending email with a subject like "The
>cgf> continual degradation of stabs with gcc" or something like that?
>cgf> I'd do it but then someone would ask for details...
>
>Well, gcc has a process in place: I file P1 bugs, I mark them as "[3.4
>regression]", Mark Mitchell in his capacity as release manager tracks
>all the regression bugs. We can't really make other people fix bugs.
>Look to our own house; the number of open gdb bugs goes up and up and
>up.
You seem to be discounting the impact of email which summarizes a trend.
Everyone knows that gcc is getting slower and slower, too. There may
even be bugs filed against that fact. But often when someone posts hard
facts showing the trend, there is a flurry of interest and activity. I'm
sure that the gdb community would respond similarly.
Anyway, you asked for suggestions on what you could do. I responded. I
certainly know how the free software world works and wasn't suggesting
that we could force anyone to do anything.
cgf
next prev parent reply other threads:[~2003-09-13 0:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 0:17 Michael Elizabeth Chastain
2003-09-13 0:36 ` Christopher Faylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-13 0:40 Michael Elizabeth Chastain
2003-09-12 22:24 Michael Elizabeth Chastain
2003-09-13 0:01 ` Christopher Faylor
2003-09-12 18:33 Michael Elizabeth Chastain
2003-09-12 8:11 Michael Elizabeth Chastain
2003-09-12 14:33 ` Daniel Jacobowitz
2003-09-12 21:05 ` Christopher Faylor
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=20030913003648.GD26022@redhat.com \
--to=cgf@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.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