From: "Giovanni Bajo" <rasky@develer.com>
To: "chris jefferson" <caj@cs.york.ac.uk>, "Mike Stump" <mrs@apple.com>
Cc: "Janis Johnson" <janis187@us.ibm.com>,
"Mark Mitchell" <mark@codesourcery.com>, <gcc@gcc.gnu.org>
Subject: Re: Mainline in regression-fix mode after Thanksgiving
Date: Wed, 24 Nov 2004 18:49:00 -0000 [thread overview]
Message-ID: <0cca01c4d252$7fa138c0$f503030a@mimas> (raw)
In-Reply-To: <41A3B68A.5020408@cs.york.ac.uk>
chris jefferson <caj@cs.york.ac.uk> wrote:
> While I might be missing something obvious, how do you intend to tell?
There are several ways.
Bugmasters have access to an automatic regression tester (by Phil) on
x86-linux which finds the single day on which a regression appeared. Given
there, looking at a ChangeLog is usually enough to spot the offending patch.
Janis reghunt is even more accurate, and it is public (it is in
gcc/contrib).
As I said, bugmasters already find out the offending patch for most
regressions, so the question here is whether we want to auto-assign them or
not. If people thinks this is a SC decision, then I would like to request an
official SC statement on this. Otherwise, we are waiting for a maintainer to
step in and say that he does not like to have regressions auto-assigned to
him and why.
--
Giovanni Bajo
next prev parent reply other threads:[~2004-11-24 18:22 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 1:16 Mark Mitchell
2004-11-23 1:21 ` Kazu Hirata
2004-11-23 1:28 ` Diego Novillo
2004-11-23 1:31 ` Mark Mitchell
2004-11-23 1:37 ` Diego Novillo
2004-11-23 11:46 ` Nathan Sidwell
2004-11-23 16:09 ` Mark Mitchell
2004-11-23 2:15 ` Mike Stump
2004-11-23 2:31 ` Mark Mitchell
2004-11-23 3:00 ` Giovanni Bajo
2004-11-23 8:17 ` Daniel Berlin
2004-11-23 8:39 ` H. J. Lu
2004-11-23 17:19 ` Janis Johnson
2004-11-23 17:23 ` Giovanni Bajo
2004-11-23 18:02 ` Mark Mitchell
2004-11-23 18:20 ` Joe Buck
2004-11-23 18:34 ` Giovanni Bajo
2004-11-23 19:01 ` Joe Buck
2004-11-25 15:47 ` Gerald Pfeifer
2004-11-23 18:03 ` Janis Johnson
2004-11-23 22:14 ` Mike Stump
[not found] ` <41A3B68A.5020408@cs.york.ac.uk>
2004-11-23 23:52 ` Mike Stump
2004-11-24 18:49 ` Giovanni Bajo [this message]
2004-11-24 19:39 ` Joe Buck
2004-11-24 18:44 ` Giovanni Bajo
2004-11-25 12:41 ` Richard Sandiford
2004-11-25 18:03 ` Mike Stump
2004-11-28 13:02 ` Toon Moene
2004-11-24 17:29 ` Joseph S. Myers
2004-11-24 17:32 ` Mark Mitchell
2004-11-24 17:38 ` Gabriel Dos Reis
2004-11-28 12:59 ` Toon Moene
2004-11-29 5:02 ` Mark Mitchell
2004-11-29 11:30 ` Richard Earnshaw
2004-11-29 13:53 ` Paul Brook
2004-11-29 14:06 ` Richard Earnshaw
2004-11-29 16:07 ` Andreas Schwab
2004-11-29 21:47 ` Phil Edwards
2004-11-29 21:59 ` Paul Brook
2004-11-29 23:27 ` Phil Edwards
2004-11-30 22:49 ` Gerald Pfeifer
2004-11-23 20:05 Richard Kenner
2004-11-28 13:41 Richard Kenner
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='0cca01c4d252$7fa138c0$f503030a@mimas' \
--to=rasky@develer.com \
--cc=caj@cs.york.ac.uk \
--cc=gcc@gcc.gnu.org \
--cc=janis187@us.ibm.com \
--cc=mark@codesourcery.com \
--cc=mrs@apple.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).