Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
	Gary Benson <gbenson@redhat.com>,
	       Stan Shebs <stanshebs@earthlink.net>,
	gdb@sourceware.org
Subject: Re: Patchwork patch tracking system
Date: Tue, 29 Apr 2014 19:33:00 -0000	[thread overview]
Message-ID: <535FF637.1080405@redhat.com> (raw)
In-Reply-To: <8738gw6p4b.fsf@fleche.redhat.com>

On 04/29/2014 06:07 PM, Tom Tromey wrote:

> I've been trying the patchworks install as well.  I don't find it all
> that useful myself, but maybe it would be better if more people were
> using it.

I've been trying it out too.  I've already found it useful to keep
track of which of my own patches I have pending.

I've been absent a little while from review, but I'm heading back,
and I'm using patchwork to guide me.

I like that it doesn't make the mailing list a second class
citizen.  I'd be willing to continue giving it a try, but indeed I
think it'd be better if more people were using it.  That'll be true
for any tool we end up with.

In the past week, I've been cleaning it up whenever I see that
patches have been pushed, even those that I didn't approve myself,
but of course it'd be better if who approves the patch or
the submitter themselves take care of their own patches.

non-maintainers shouldn't hold back from creating an account
and updating the state of their own patches.  Whatever helps
bringing the load down from maintainers should help your own
patches.  :-)

Here's the current list of who-has-how-many-pending:

$ ~/bin/pwclient-hacked list -s New | sort | uniq -c | sort -nr
     35 Andy Wingo <wingo@igalia.com>
     24 Andreas Arnez <arnez@linux.vnet.ibm.com>
     20 Yao Qi <yao@codesourcery.com>
     17 Jan Kratochvil <jan.kratochvil@redhat.com>
     16 Pedro Alves <palves@redhat.com>
     14 Siva Chandra <sivachandra@google.com>
     13 Keith Seitz <keiths@redhat.com>
     13 David Blaikie <dblaikie@gmail.com>
     12 Andrew Burgess <aburgess@broadcom.com>
      9 Doug Evans <dje@google.com>
      4 Kyle McMartin <kmcmarti@redhat.com>
      4 Hui Zhu <hui_zhu@mentor.com>
      3 Simon Marchi <simon.marchi@ericsson.com>
      3 Eli Zaretskii <eliz@gnu.org>
      3 Alan Modra <amodra@gmail.com>
      2 Ulrich Weigand <uweigand@de.ibm.com>
      2 Mike Frysinger <vapier@gentoo.org>
      2 Doug Evans <xdje42@gmail.com>
      2 Alexander Smundak <asmundak@google.com>
      2 Agovic, Sanimir <sanimir.agovic@intel.com>
      1 Vladimir Nikulichev <nvs@tbricks.com>
      1 Tom Tromey <tromey@redhat.com>
      1 Sandra Loosemore <sandra@codesourcery.com>
      1 Pierre Langlois <pierre.langlois@embecosm.com>
      1 Nick Clifton <nickc@redhat.com>
      1 Mateusz Tabaka <8tab@wp.pl>
      1 Mark Wielaard <mjw@redhat.com>
      1 Marcus Shawcroft <marcus.shawcroft@arm.com>
      1 Marc Khouzam <marc.khouzam@ericsson.com>
      1 Maciej W. Rozycki <macro@codesourcery.com>
      1 Julian Brown <julian@codesourcery.com>
      1 John Marino <gnugcc@marino.st>
      1 Gary Benson <gbenson@redhat.com>
      1 David Taylor <dtaylor@emc.com>
      1 Daniel Gutson <daniel.gutson@tallertechnologies.com>

As you see, most of the patches so far, since we began tracking a
few weeks back, came from a small set of people.  And I suspect
many of those are actually already in.

-- 
Pedro Alves


  parent reply	other threads:[~2014-04-29 18:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02 10:08 Gary Benson
2014-04-04 22:50 ` Stan Shebs
2014-04-17 18:18   ` Gary Benson
2014-04-22 15:40     ` Joel Brobecker
2014-04-22 15:51       ` Eric Christopher
2014-04-22 18:37         ` Joel Brobecker
2014-04-24 11:42           ` Siva Chandra
2014-08-02 14:25             ` Mike Frysinger
2014-04-29 17:25       ` Tom Tromey
2014-04-29 17:36         ` Eli Zaretskii
2014-04-29 18:58         ` Joel Brobecker
2014-04-30  9:19           ` Gary Benson
2014-04-30 12:45             ` Joel Brobecker
2014-04-29 19:33         ` Pedro Alves [this message]
2014-04-29 22:32           ` Breazeal, Don
2014-04-30  1:08             ` Pedro Alves
2014-04-30  3:45               ` Breazeal, Don
2014-05-21 14:47         ` Tom Tromey
2014-05-21 17:18           ` Pedro Alves
2014-05-21 17:49             ` Joel Brobecker
2014-05-21 18:03             ` Eli Zaretskii
2014-05-21 18:23               ` Joel Brobecker
2014-05-21 18:48                 ` Eli Zaretskii
2014-05-21 19:45                   ` Joel Brobecker
2014-05-21 21:35               ` Pedro Alves

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=535FF637.1080405@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gbenson@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=stanshebs@earthlink.net \
    --cc=tromey@redhat.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