public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Giovanni Bajo" <rasky@develer.com>
To: "Janis Johnson" <janis187@us.ibm.com>,
	"Mark Mitchell" <mark@codesourcery.com>
Cc: <mrs@apple.com>, <gcc@gcc.gnu.org>
Subject: Re: Mainline in regression-fix mode after Thanksgiving
Date: Tue, 23 Nov 2004 17:23:00 -0000	[thread overview]
Message-ID: <095801c4d180$19e95e40$f503030a@mimas> (raw)
In-Reply-To: <20041123170139.GA4463@us.ibm.com>

Janis Johnson <janis187@us.ibm.com> wrote:


> I'm set up to do regression hunts on a powerpc64-linux-gnu system and
> can keep it busy.  For regressions that can be tested with only cc1 or
> cc1plus a regression hunt can build and test cross compilers so it
> doesn't matter what the build/host system is.

Great!

> If there are regressions you'd like me to track down, assign the PRs to
> me temporarily and then I can assign them to the person who introduced
> or exposed the bug, or to someone else who can then decide what do with
> it next.

As I said in another mail in this thread, we do not have a policy so that we
can automatically assign regressions to the author of the patch which
caused/exposed them. (Re)Assigning a bug without permission is considered
unpolite by some people.

Note that I do not agree. If Mark Mitchell agrees, we can setup a policy to
do so. For many regressions present in Bugzilla, we already know which patch
caused it (thanks mainly to Volker and Andrew), so assigning them in
Bugzilla could be a good way to make this more visible. Right now, we
usually just CC: the person that caused the regression notifying him/her.
-- 
Giovanni Bajo

  reply	other threads:[~2004-11-23 17:16 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 [this message]
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
2004-11-24 18:44           ` Giovanni Bajo
2004-11-25 12:41             ` Richard Sandiford
2004-11-25 18:03               ` Mike Stump
     [not found]           ` <41A3B68A.5020408@cs.york.ac.uk>
2004-11-23 23:52             ` Mike Stump
2004-11-24 18:49             ` Giovanni Bajo
2004-11-24 19:39               ` Joe Buck
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='095801c4d180$19e95e40$f503030a@mimas' \
    --to=rasky@develer.com \
    --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).