From: NightStrike <nightstrike@gmail.com>
To: Joern Rennecke <joern.rennecke@embecosm.com>
Cc: Eric Botcazou <ebotcazou@adacore.com>, gcc@gcc.gnu.org
Subject: Re: Patch pinging
Date: Mon, 07 Jun 2010 20:33:00 -0000 [thread overview]
Message-ID: <AANLkTily7hPcIpr52rKH_sBfFBHshgM4ZM3Zy4_2Uj6r@mail.gmail.com> (raw)
In-Reply-To: <20100607162348.wzulrgczs4sc8o4o-nzlynne@webmail.spamcop.net>
On Mon, Jun 7, 2010 at 4:23 PM, Joern Rennecke
<joern.rennecke@embecosm.com> wrote:
> Quoting NightStrike <nightstrike@gmail.com>:
>
>> Annoying or not, I wasn't offering to sift through svn commit logs.
>
> How about requiring that a patch should have an associated open PR with the
> patch keyword to be considered for pinging.
> Then you can do a bugzilla search for all open PRs with the patch keyword.
>
I suggested that a long time ago on irc, but was brutally shot down
for it. Apparently, most people hate bugzilla :( To be clear, what I
suggested was that every patch should have a PR. There is way too
much duplication of purpose between bugzilla, gcc-bugs, and
gcc-patches.
TBH, I was sort of doing this manually to start for Jakub's patches
that had a PR with "Fixed" at the bottom of them. I didn't ping on
any of those. That was extra work, but it was doable.
Reading gcc-cvs, or ChangeLogs, or other things like that is just way
too much time.
next prev parent reply other threads:[~2010-06-07 20:27 UTC|newest]
Thread overview: 112+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 19:00 NightStrike
2010-06-02 20:54 ` Diego Novillo
2010-06-07 14:17 ` NightStrike
2010-06-07 14:26 ` Martin Guy
2010-06-07 15:00 ` Ian Lance Taylor
2010-06-07 19:24 ` Eric Botcazou
2010-06-07 19:36 ` NightStrike
2010-06-07 19:40 ` Eric Botcazou
2010-06-07 20:27 ` Paolo Carlini
2010-06-07 20:33 ` Ian Lance Taylor
2010-06-07 21:16 ` Jeff Law
2010-06-07 21:22 ` Paolo Carlini
2010-06-07 21:43 ` Ian Lance Taylor
2010-06-08 1:13 ` Manuel López-Ibáñez
2010-06-08 4:43 ` Paolo Carlini
2010-06-08 15:21 ` NightStrike
2010-06-08 15:32 ` Jeff Law
2010-06-08 15:50 ` David Edelsohn
2010-06-08 19:21 ` Basile Starynkevitch
2010-06-08 19:32 ` Paolo Carlini
2010-06-08 5:44 ` Ben White
2010-06-08 7:35 ` Chiheng Xu
2010-06-08 9:18 ` Manuel López-Ibáñez
2010-06-08 15:53 ` H.J. Lu
2010-06-08 15:55 ` Manuel López-Ibáñez
2010-06-08 18:41 ` Tobias Burnus
2010-06-09 6:13 ` Chiheng Xu
2010-06-27 9:44 ` Gerald Pfeifer
2010-06-27 9:55 ` Tobias Burnus
2010-06-27 12:51 ` Manuel López-Ibáñez
2010-06-27 17:45 ` Richard Guenther
2010-06-27 19:33 ` David Edelsohn
2010-06-27 21:18 ` Manuel López-Ibáñez
2010-06-28 7:28 ` David Edelsohn
2010-06-28 8:51 ` NightStrike
2010-06-28 13:02 ` David Edelsohn
2010-06-28 14:23 ` NightStrike
2010-06-28 20:02 ` David Edelsohn
2010-06-28 20:11 ` NightStrike
2010-06-28 21:00 ` Basile Starynkevitch
2010-06-28 21:25 ` David Edelsohn
2010-06-28 21:25 ` Richard Kenner
2010-06-28 21:25 ` Tobias Burnus
2010-06-28 21:43 ` Manuel López-Ibáñez
2010-06-28 21:56 ` Basile Starynkevitch
2010-06-28 22:33 ` Richard Kenner
2010-06-28 22:37 ` Joseph S. Myers
2010-06-28 23:53 ` Ian Lance Taylor
2010-06-29 5:53 ` NightStrike
2010-06-29 7:04 ` Ian Lance Taylor
2010-06-29 11:35 ` Richard Kenner
2010-06-29 11:49 ` NightStrike
2010-06-29 15:06 ` Ian Lance Taylor
2010-06-29 16:47 ` NightStrike
2010-06-29 16:50 ` Ian Lance Taylor
2010-06-29 22:50 ` Jonathan Corbet
2010-06-30 5:05 ` Ian Lance Taylor
2010-07-01 5:22 ` Mark Mitchell
2010-07-01 11:57 ` Richard Kenner
2010-07-01 12:18 ` Robert Dewar
2010-07-01 12:34 ` Jonathan Corbet
2010-06-29 9:38 ` Jonathan Wakely
2010-06-29 12:01 ` NightStrike
2010-06-29 11:27 ` Manuel López-Ibáñez
2010-06-29 11:29 ` NightStrike
2010-06-29 14:09 ` Manuel López-Ibáñez
2010-06-29 14:29 ` NightStrike
2010-06-29 16:38 ` Ian Lance Taylor
2010-06-28 16:29 ` NightStrike
2010-06-28 17:13 ` Paolo Carlini
2010-06-30 17:44 ` Frank Ch. Eigler
2010-06-30 17:57 ` NightStrike
2010-06-30 18:02 ` Paolo Carlini
2010-06-30 19:16 ` NightStrike
2010-06-30 19:24 ` Paolo Carlini
2010-06-30 19:31 ` Paolo Carlini
2010-06-30 19:45 ` David Edelsohn
2010-06-30 20:38 ` NightStrike
2010-07-01 10:44 ` Paolo Bonzini
2010-07-01 12:33 ` Richard Kenner
2010-06-28 22:35 ` Gerald Pfeifer
2010-06-28 22:46 ` David Edelsohn
2010-06-08 7:32 ` Basile Starynkevitch
2010-06-08 7:42 ` Jonathan Wakely
2010-06-08 9:18 ` Paolo Bonzini
2010-06-08 11:17 ` Manuel López-Ibáñez
2010-06-08 11:30 ` Manuel López-Ibáñez
2010-06-08 20:33 ` Basile Starynkevitch
2010-06-08 20:37 ` Paolo Bonzini
2010-06-08 23:04 ` Dave Korn
2010-06-10 20:03 ` Gerald Pfeifer
2010-06-07 21:16 ` Paolo Carlini
2010-06-07 21:23 ` Ian Lance Taylor
2010-06-07 21:40 ` Paolo Carlini
2010-06-07 22:21 ` Andrew Pinski
2010-06-08 0:20 ` Paolo Carlini
2010-06-08 0:35 ` Manuel López-Ibáñez
2010-06-07 22:22 ` Ian Lance Taylor
2010-06-08 13:10 ` Jonathan Wakely
2010-06-10 20:26 ` Quentin Neill
2010-06-14 16:44 ` Manuel López-Ibáñez
2010-06-14 17:14 ` NightStrike
2010-06-14 22:08 ` Quentin Neill
2010-06-07 20:31 ` Steven Bosscher
[not found] ` <20100607162348.wzulrgczs4sc8o4o-nzlynne@webmail.spamcop.net>
2010-06-07 20:33 ` NightStrike [this message]
2010-06-07 21:05 ` Joseph S. Myers
2010-06-08 9:14 ` Eric Botcazou
2010-06-08 15:08 ` NightStrike
2010-06-08 18:43 ` Eric Botcazou
2010-06-09 0:52 ` Martin Guy
2010-06-09 7:31 ` NightStrike
2010-06-09 21:12 ` Martin Guy
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=AANLkTily7hPcIpr52rKH_sBfFBHshgM4ZM3Zy4_2Uj6r@mail.gmail.com \
--to=nightstrike@gmail.com \
--cc=ebotcazou@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=joern.rennecke@embecosm.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).