From: Fam Zheng <famz@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org,
"Richard W . M . Jones" <rjones@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 0/2] block/ssh: Implement .bdrv_refresh_filename()
Date: Thu, 8 Mar 2018 10:12:41 +0800 [thread overview]
Message-ID: <20180308021241.GM13844@lemon.usersys.redhat.com> (raw)
In-Reply-To: <2d97780c-4a06-1b08-8211-760fc3567c2a@redhat.com>
On Wed, 03/07 12:50, John Snow wrote:
> It's something I'd like to see patchew do, actually:
>
> "Here's a list of what's on the list that has no reviews or NACKs, and
> needs some love"
It's not hard to define a search condition for that:
http://patchew.org/search-help
http://patchew.org/search?q=project%3AQEMU+age%3A%3E1m+not%3Areviewed+not%3Areplied+not%3Amerged+is%3Atested+to%3Aqemu-block
>
> coupled with a 30 day "Hey, nobody looked at this" ping to the list
> before it NACKs a set for being too old.
If the initial landing of the patch didn't get enough attention, chances are the
pings will not change much about it especially it's from a bot.
A summary list sounds good, though.
Fam
next prev parent reply other threads:[~2018-03-08 2:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 20:22 [Qemu-devel] [PATCH 0/2] block/ssh: Implement .bdrv_refresh_filename() Max Reitz
2018-02-05 20:22 ` [Qemu-devel] [PATCH 1/2] " Max Reitz
2018-02-05 20:22 ` [Qemu-devel] [PATCH 2/2] block/ssh: Implement .bdrv_dirname() Max Reitz
2018-02-05 20:45 ` [Qemu-devel] [PATCH 0/2] block/ssh: Implement .bdrv_refresh_filename() Richard W.M. Jones
2018-02-05 20:46 ` Richard W.M. Jones
2018-02-05 20:56 ` Max Reitz
2018-03-06 21:51 ` [Qemu-devel] [Qemu-block] " John Snow
2018-03-07 10:04 ` Kevin Wolf
2018-03-07 17:50 ` John Snow
2018-03-08 2:12 ` Fam Zheng [this message]
2018-03-12 15:47 ` John Snow
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=20180308021241.GM13844@lemon.usersys.redhat.com \
--to=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
/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).