From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Fwd: Proposal: Improving patch tracking and review using Rietveld
Date: Thu, 27 Jan 2011 10:34:18 +0000 [thread overview]
Message-ID: <AANLkTinSJ-ABU7dEEiHuuWQrvNf_w3rMXOacnPaVh3mO@mail.gmail.com> (raw)
In-Reply-To: <4D41479D.4060809@gnu.org>
On Thu, Jan 27, 2011 at 10:23 AM, Paolo Bonzini <bonzini@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 implemented in QEMU, this may
>>> be a more interesting possibility.
>>
>> What features are you looking for beyond archiving?
>
> Well, you pretty much nailed it.
Glad we're on the same page. I wanted to see if you are looking for
code review or patch tracking.
I actually like the code review process used today - inline patches to
the mailing list. It's hard to add value to that without making it
more cumbersome.
But patch tracking is definitely lacking and would benefit from
something that aggregates and presents an accurate view of the state
of unapplied patches.
Stefan
next prev parent reply other threads:[~2011-01-27 10:42 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 [this message]
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
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=AANLkTinSJ-ABU7dEEiHuuWQrvNf_w3rMXOacnPaVh3mO@mail.gmail.com \
--to=stefanha@gmail.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 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 NNTP newsgroup(s).