From: Ranjit Mathew <rmathew@gmail.com>
To: gcc@gcc.gnu.org
Subject: Re: [RFC] Auto-assign regressions (maintainers, read!)
Date: Fri, 26 Nov 2004 08:52:00 -0000 [thread overview]
Message-ID: <co6l83$djj$1@sea.gmane.org> (raw)
In-Reply-To: <84fc9c000411250144650a2a46@mail.gmail.com>
Richard Guenther wrote:
>
> Can't we have a caused-by-patch field in bugzilla where we could link the patch
> causing the failure and a caused-by field with the author (and
> automatically CC'ing
> him)? I don't think it is a great idea overloading the assigned-to field.
IMHO it'd be better to just have a new keyword instead and put
the link to the offending patch in the body of the PR; just as
it is done with the "patch" keyword for PRs that have a patch
pending review.
Ranjit.
--
Ranjit Mathew Email: rmathew AT gmail DOT com
Bangalore, INDIA. Web: http://ranjitmathew.tripod.com/
next prev parent reply other threads:[~2004-11-26 7:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 2:03 Giovanni Bajo
2004-11-25 10:17 ` Richard Guenther
2004-11-25 16:35 ` Daniel Berlin
2004-11-25 16:47 ` Richard Guenther
2004-11-25 16:57 ` Andrew MacLeod
2004-11-25 17:41 ` Dave Korn
2004-11-29 3:26 ` Kai Henningsen
2004-11-29 4:17 ` bobby mcnulty junior
2004-11-26 8:52 ` Ranjit Mathew [this message]
2004-11-25 14:03 ` Diego Novillo
2004-11-27 3:27 ` Ian Lance Taylor
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='co6l83$djj$1@sea.gmane.org' \
--to=rmathew@gmail.com \
--cc=gcc@gcc.gnu.org \
/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).