public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
Cc: Janis Johnson <janis187@us.ibm.com>, gcc@gcc.gnu.org, rodrigc@attbi.com
Subject: Re: regression hunt status, question about reports to mailing list
Date: Fri, 20 Dec 2002 13:14:00 -0000	[thread overview]
Message-ID: <20021220110324.A13520@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0212201120580.18387-100000@gandalf.ticam.utexas.edu>; from bangerth@ticam.utexas.edu on Fri, Dec 20, 2002 at 11:27:07AM -0600

On Fri, Dec 20, 2002 at 11:27:07AM -0600, Wolfgang Bangerth wrote:
> 
> (Janis wrote:)
> > Should I continue to send mail to gcc@gcc.gnu.org when I identify the
> > patch that caused a regression or that fixed a mainline regression that
> > still exists on a release branch?  This seemed like a good idea when
> > there was one every couple of days, but I'm continuing to discover
> > short-cuts that make it faster and easier, so the trickle of mail might
> > be getting large enough to be annoying
> 
> I think you should. I guess, some nagging is ok, after all we haven't seen 
> a rush to fix the regressions for which the offending patch has been 
> identified. Yesterday, we had 90 (!) listed regressions, and little 
> movement to get them fixed (except for Eric's noticable work on the 
> optimization bugs). A little public pressure seems appropriate.

The people I've notified are all very active contributors to GCC, and it
doesn't surprise me that they haven't fixed the regressions immediately.
I don't expect them to need nagging, but we should certainly remind them
about remaining regressions when we get close to deadlines.  It's also
quite possible that the people who fix the bugs will not be the ones
whose patches caused them to show up.

Janis

  reply	other threads:[~2002-12-20 19:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-20 11:29 Janis Johnson
2002-12-20 11:52 ` Wolfgang Bangerth
2002-12-20 13:14   ` Janis Johnson [this message]
2002-12-20 13:16     ` Wolfgang Bangerth
2002-12-20 15:17       ` Joe Buck
2002-12-20 15:58         ` Wolfgang Bangerth
2002-12-23  5:15 ` Mark Mitchell
2002-12-23 17:37   ` Tom Lord
2002-12-27  0:26 ` Kaveh R. Ghazi
2002-12-28 11:48   ` Janis Johnson

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=20021220110324.A13520@us.ibm.com \
    --to=janis187@us.ibm.com \
    --cc=bangerth@ticam.utexas.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=rodrigc@attbi.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).