qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: make a few more tests generic
Date: Fri, 10 Jul 2009 08:39:37 -0500	[thread overview]
Message-ID: <4A574499.3010907@us.ibm.com> (raw)
In-Reply-To: <20090710133431.GA17096@lst.de>

Christoph Hellwig wrote:
>> It's also up to the submitter to keep track of their patches.  If they 
>> think one should be applied that hasn't been, they need to follow up on it. 
>> The only way to scale here is to push as much work as possible to the 
>> outer-most nodes.
>>     
>
> It's just really hard to track stuff without feedback.  You only flush
> your queue very sproadicly, so some kind of indicator that it is in the
> queue would be extremly helpful.  Just an ok, I'll queue it to mean that
> it's not lost means we know it's been deal with in some way, and we can
> ping patches that haven't gotten any feedback for say a week.
>   

What about akpm-style automated notifications that a patch has been 
queued and/or rejected from queue?  These would just go to the sender, 
not the list.

It wouldn't be very hard for me to add this.

And yeah, more frequent queue flushing is a separate problem.

-- 
Regards,

Anthony Liguori

  reply	other threads:[~2009-07-10 13:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 19:41 [Qemu-devel] [PATCH] qemu-iotests: make a few more tests generic Christoph Hellwig
2009-07-09  9:58 ` Kevin Wolf
2009-07-09 13:25   ` Christoph Hellwig
2009-07-10  7:47     ` Kevin Wolf
2009-07-10 10:00       ` Christoph Hellwig
2009-07-10 12:50       ` Anthony Liguori
2009-07-10 13:10         ` Kevin Wolf
2009-07-10 13:34         ` Christoph Hellwig
2009-07-10 13:39           ` Anthony Liguori [this message]
2009-07-10 14:27             ` Christoph Hellwig

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=4A574499.3010907@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=hch@lst.de \
    --cc=kwolf@redhat.com \
    --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).