From: Kashyap Chamarthy <kchamart@redhat.com>
To: Alberto Garcia <berto@igalia.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: Plans to bring QMP 'x-blockdev-reopen' out of experimental?
Date: Tue, 20 Oct 2020 10:20:09 +0200 [thread overview]
Message-ID: <20201020082009.GG600839@paraplu> (raw)
In-Reply-To: <w51mu0ifbuf.fsf@maestria.local.igalia.com>
On Mon, Oct 19, 2020 at 05:56:56PM +0200, Alberto Garcia wrote:
> On Tue 06 Oct 2020 11:10:01 AM CEST, Kashyap Chamarthy wrote:
> > Hi, folks
> >
> > If this was already discussed on the list, please point me to the
> > thread. I took a quick look at my local archives, I didn't find any,
> > besides patches to tests.
>
> I think this is the last time that I was discussed:
>
> https://lists.gnu.org/archive/html/qemu-block/2020-02/msg00558.html
>
> And this one in particular:
>
> https://lists.gnu.org/archive/html/qemu-block/2020-02/msg00601.html
>
> But Kevin fixed this one month later:
>
> https://lists.gnu.org/archive/html/qemu-block/2020-03/msg00266.html
Ah, thanks for these URLs, Berto. My bad, I didn't find it in my local
archives because of the way I organized my mail filters; I recently
cleared the 'qemu-block' maildir, so these didn't show up.
--
/kashyap
prev parent reply other threads:[~2020-10-20 8:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201006091001.GA64583@paraplu>
2020-10-19 15:56 ` Plans to bring QMP 'x-blockdev-reopen' out of experimental? Alberto Garcia
2020-10-19 16:46 ` Alberto Garcia
2020-10-20 8:23 ` Kevin Wolf
2020-10-20 11:53 ` Alberto Garcia
2020-10-21 10:48 ` Kevin Wolf
2020-12-02 16:12 ` Alberto Garcia
2020-12-02 16:28 ` Kevin Wolf
2020-12-02 16:40 ` Alberto Garcia
2020-12-02 17:51 ` Kevin Wolf
2020-12-04 14:03 ` Alberto Garcia
2020-10-20 8:20 ` Kashyap Chamarthy [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=20201020082009.GG600839@paraplu \
--to=kchamart@redhat.com \
--cc=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.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).