public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@redhat.com>
To: "Giovanni Bajo" <rasky@develer.com>
Cc: "Mike Stump" <mrs@apple.com>,
	"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: Thu, 25 Nov 2004 12:41:00 -0000	[thread overview]
Message-ID: <wvn653ucinc.fsf@talisman.cambridge.redhat.com> (raw)
In-Reply-To: <0cbe01c4d252$03240520$f503030a@mimas> (Giovanni Bajo's message of "Wed, 24 Nov 2004 19:18:35 +0100")

"Giovanni Bajo" <rasky@develer.com> writes:
> Mike Stump <mrs@apple.com> wrote:
>> So, let me ask if anyone who puts in patches would object to having
>> regressions assigned to them?  If no one objects, I'd say, lets just
>> make it policy.
>
> Any takers?

Well, I don't object to anyone doing this for my patches, but I really
do think Joe's description of how the assigned field should work is better.

For example, if I'm in a bug-fixing mood, the first thing I'll do is
search bugzilla for MIPS PRs.  And since this is something I do in my
spare time, I don't want to waste it by duplicating other people's work.
So I'll pick the bugs that aren't yet assigned to anyone.

You (Giovanni) say that people could just unassign themselves if they
don't plan to look at a PR soon.  Although that's clearly the case _in
principle_, in practice, this often doesn't happen.  There are several
target-independent bugs with a MIPS target field that have been assigned
(to non-MIPS maintainers) for many months without any apparent action.

[No criticism implied, btw.  I'm not whiter than white here.]

As I think Joe said, if the PR trail already mentions the patch that
caused a regression, putting the name of the patch author in the assigned
field doesn't add any more information.  It actually removes information,
because PRs then go into an uncertain "is anyone really going to look at
this or not?" state.

Richard

  reply	other threads:[~2004-11-25 10:46 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
2004-11-24 18:44           ` Giovanni Bajo
2004-11-25 12:41             ` Richard Sandiford [this message]
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=wvn653ucinc.fsf@talisman.cambridge.redhat.com \
    --to=rsandifo@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=janis187@us.ibm.com \
    --cc=mark@codesourcery.com \
    --cc=mrs@apple.com \
    --cc=rasky@develer.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).