From: John Snow <jsnow@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Max Reitz <mreitz@redhat.com>,
qemu-block@nongnu.org,
"Richard W . M . Jones" <rjones@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 0/2] block/ssh: Implement .bdrv_refresh_filename()
Date: Wed, 7 Mar 2018 12:50:36 -0500 [thread overview]
Message-ID: <2d97780c-4a06-1b08-8211-760fc3567c2a@redhat.com> (raw)
In-Reply-To: <20180307100424.GA7917@localhost.localdomain>
On 03/07/2018 05:04 AM, Kevin Wolf wrote:
> Am 06.03.2018 um 22:51 hat John Snow geschrieben:
>> On 02/05/2018 03:22 PM, Max Reitz wrote:
>>> This series implements .bdrv_refresh_filename() for the ssh block
>>> driver, along with an appropriate .bdrv_dirname() so we don't chop off
>>> query strings for backing files with relative filenames.
>>>
>>> This series depends on my “block: Fix some filename generation issues”
>>> series and on Pino's “ssh: switch from libssh2 to libssh” patch.
>>>
>>> Based-on: 20180205151835.20812-1-mreitz@redhat.com
>>> Based-on: 20180118164439.2120-1-ptoscano@redhat.com
>>>
>>>
>>> Max Reitz (2):
>>> block/ssh: Implement .bdrv_refresh_filename()
>>> block/ssh: Implement .bdrv_dirname()
>>>
>>> block/ssh.c | 72 +++++++++++++++++++++++++++++++++++++++++++++++++++++++------
>>> 1 file changed, 65 insertions(+), 7 deletions(-)
>>
>> Did this one rot on the vine?
>>
>>> 1 month old.
>
> The Based-on tags are the problem, in particular the first one. But yes,
> we could possibly do more to review the dependencies...
>
> Kevin
>
Yeah, sorry, I'm not pulling my review weight right now. I do try to
keep my block-devel inbox a rough "todo," though, so for patches that
get to that one month mark with no conclusion I like to ping them before
I archive them.
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"
coupled with a 30 day "Hey, nobody looked at this" ping to the list
before it NACKs a set for being too old.
I hope nobody reads these >1 month pings as me wondering why nobody ELSE
has reviewed it, which is not my intent...
--js
next prev parent reply other threads:[~2018-03-07 17:50 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 [this message]
2018-03-08 2:12 ` Fam Zheng
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=2d97780c-4a06-1b08-8211-760fc3567c2a@redhat.com \
--to=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).