From: Stefan Hajnoczi <stefanha@gmail.com>
To: Anthony Liguori <aliguori@linux.vnet.ibm.com>
Cc: Paolo Bonzini <bonzini@gnu.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Fwd: Proposal: Improving patch tracking and review using Rietveld
Date: Thu, 27 Jan 2011 19:40:38 +0000 [thread overview]
Message-ID: <AANLkTimm2F_9KDHqxKs=eh=KKCDkzMGyC=kvHopPPB68@mail.gmail.com> (raw)
In-Reply-To: <4D41ABFF.7050606@linux.vnet.ibm.com>
On Thu, Jan 27, 2011 at 5:31 PM, Anthony Liguori
<aliguori@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, you end up with a terrible backlog
>
> 2) it doesn't understand patches series. A 20 patch series gets applied all
> at once, yet you have to update status for each patch. That's annoying.
You shouldn't have to update patch status manually at all. If there
is a manual step involved then it is unlikely that patchwork's view
will ever stay in sync with the actual repository.
Stefan
prev parent reply other threads:[~2011-01-28 7:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 7:55 [Qemu-devel] Fwd: Proposal: Improving patch tracking and review using Rietveld Paolo Bonzini
2011-01-27 10:19 ` Stefan Hajnoczi
2011-01-27 10:23 ` Paolo Bonzini
2011-01-27 10:34 ` Stefan Hajnoczi
2011-01-27 16:26 ` [Qemu-devel] " Paolo Bonzini
2011-01-27 16:31 ` Diego Novillo
2011-01-27 17:31 ` [Qemu-devel] " Anthony Liguori
2011-01-27 18:32 ` Peter Maydell
2011-01-27 19:40 ` Stefan Hajnoczi [this message]
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='AANLkTimm2F_9KDHqxKs=eh=KKCDkzMGyC=kvHopPPB68@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=bonzini@gnu.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.