From: Thomas Huth <thuth@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: jsnow@redhat.com
Subject: Re: [PATCH 0/3] scripts/qmp/qom-fuse: Scrape off the bitrot
Date: Thu, 23 Jul 2020 17:21:07 +0200 [thread overview]
Message-ID: <36a450fb-8072-1223-9253-0446ed23dcd1@redhat.com> (raw)
In-Reply-To: <20200723142738.1868568-1-armbru@redhat.com>
On 23/07/2020 16.27, Markus Armbruster wrote:
> Markus Armbruster (3):
> scripts/qmp/qom-fuse: Unbreak import of QEMUMonitorProtocol
> scripts/qmp/qom-fuse: Port to current Python module fuse
> scripts/qmp/qom-fuse: Fix getattr(), read() for files in /
Could it be added to a CI pipeline, so that it does not bitrot again?
Thomas
next prev parent reply other threads:[~2020-07-23 15:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 14:27 [PATCH 0/3] scripts/qmp/qom-fuse: Scrape off the bitrot Markus Armbruster
2020-07-23 14:27 ` [PATCH 1/3] scripts/qmp/qom-fuse: Unbreak import of QEMUMonitorProtocol Markus Armbruster
2020-07-23 15:08 ` Philippe Mathieu-Daudé
2020-07-24 16:51 ` John Snow
2020-07-23 14:27 ` [PATCH 2/3] scripts/qmp/qom-fuse: Port to current Python module fuse Markus Armbruster
2020-07-24 16:56 ` John Snow
2020-07-27 7:09 ` Markus Armbruster
2020-07-23 14:27 ` [PATCH 3/3] scripts/qmp/qom-fuse: Fix getattr(), read() for files in / Markus Armbruster
2020-07-23 15:10 ` Philippe Mathieu-Daudé
2020-07-24 7:00 ` Markus Armbruster
2020-07-24 16:58 ` John Snow
2020-07-23 15:21 ` Thomas Huth [this message]
2020-07-24 7:33 ` Status of scripts/qmp/ (was: [PATCH 0/3] scripts/qmp/qom-fuse: Scrape off the bitrot) Markus Armbruster
2020-07-24 8:10 ` Thomas Huth
2020-07-24 16:53 ` [PATCH 0/3] scripts/qmp/qom-fuse: Scrape off the bitrot 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=36a450fb-8072-1223-9253-0446ed23dcd1@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=jsnow@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).