On Thu, Jan 27, 2011 at 08:55:30AM +0100, Paolo Bonzini wrote:
Forwarding this from the GCC mailing list. Since patchwork isn't
more than a mail archive the way it's implemented in QEMU, this may
be a more interesting possibility.
What features are you looking for beyond archiving?
It would
On 01/27/2011 11:19 AM, Stefan Hajnoczi wrote:
On Thu, Jan 27, 2011 at 08:55:30AM +0100, Paolo Bonzini wrote:
Forwarding this from the GCC mailing list. Since patchwork isn't
more than a mail archive the way it's implemented in QEMU, this may
be a more interesting possibility.
What features
On Thu, Jan 27, 2011 at 10:23 AM, Paolo Bonzini bonz...@gnu.org wrote:
On 01/27/2011 11:19 AM, Stefan Hajnoczi wrote:
On Thu, Jan 27, 2011 at 08:55:30AM +0100, Paolo Bonzini wrote:
Forwarding this from the GCC mailing list. Since patchwork isn't
more than a mail archive the way it's
On 01/27/2011 01:55 AM, Paolo Bonzini wrote:
Forwarding this from the GCC mailing list. Since patchwork isn't more
than a mail archive the way it's implemented in QEMU, this may be a
more interesting possibility.
Patchwork is a nice tool but I found a few issues with it that really
deterred
On 27 January 2011 17:31, Anthony Liguori aligu...@linux.vnet.ibm.com wrote:
Patchwork is a nice tool but I found a few issues with it that really
deterred me from using it:
2) it doesn't understand patches series. A 20 patch series gets applied all
at once, yet you have to update status for
On Thu, Jan 27, 2011 at 5:31 PM, Anthony Liguori
aligu...@linux.vnet.ibm.com wrote:
Patchwork is a nice tool but I found a few issues with it that really
deterred me from using it:
1) it's all or nothing in terms of whether maintainers use it. if everyone
isn't on top of keeping it clean,
Forwarding this from the GCC mailing list. Since patchwork isn't more
than a mail archive the way it's implemented in QEMU, this may be a more
interesting possibility.
Paolo
At Google we use a code review tool which was open sourced a couple of
years ago: Rietveld