From: Gary Benson <gbenson@redhat.com>
To: gdb@sourceware.org
Subject: Patchwork patch tracking system
Date: Wed, 02 Apr 2014 10:08:00 -0000 [thread overview]
Message-ID: <20140402100842.GA956@blade.nx> (raw)
Hi all,
Patchwork is a patch tracking system designed to help manage
contributions to open-source projects. The glibc maintainers have
been experimenting to see if it can meet their needs, and they've very
kindly added GDB to their test instance to allow us to trial it too.
The way it works is that patches sent to gdb-patches are caught by
Patchwork and appear on a web page, currently
http://patchwork.siddhesh.in/. Replies to patch emails are also
caught, and are appended to the patch pages.
The prototype workflow the glibc maintainers are using is
https://sourceware.org/glibc/wiki/Patch%20Review%20Workflow. If you'd
like to have a go with the trial instance please register an account
on http://patchwork.siddhesh.in/ and then get hold of me by email or
on IRC (I'm gbenson on Freenode) and I'll add you to the maintainers
list. You won't be able to update anything without this.
Patchwork has been subscribed to gdb-patches for a couple of weeks
now, but I haven't updated any patches' statuses so there will be some
stale ones in there. Please feel free to update patches as you see
fit, this is a trial instance so don't worry about breaking things!
As well as the web interface there is a command line client.
You can download the client script and a sample ~/.pwclientrc
from here:
http://patchwork.siddhesh.in/project/binutils-gdb/
The ~/.pwclientrc file just needs your password adding, then you
can do things like:
pwclient list -s new
to see a list of all patches with the state "new".
Let me know what you think!
Thanks,
Gary
--
http://gbenson.net/
next reply other threads:[~2014-04-02 10:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 10:08 Gary Benson [this message]
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
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=20140402100842.GA956@blade.nx \
--to=gbenson@redhat.com \
--cc=gdb@sourceware.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