From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH v1 1/2] qmp.c: (re)implement qmp_cpu
Date: Fri, 15 Dec 2017 19:11:14 +0100 [thread overview]
Message-ID: <bf9ded69-6cf6-f7bf-cfca-a31a6b784211@redhat.com> (raw)
In-Reply-To: <87ind8nlh9.fsf@dusky.pond.sub.org>
On 15/12/2017 14:56, Markus Armbruster wrote:
>
> Paolo, we have numerous Features/ pages, and I suspect many of them are
> too outdated to serve any purpose but confusing readers. In theory,
> "somebody" could go through them to identify stale ones. In practice,
> "somebody" doesn't exist, I'm afraid. Should we summarily delete
> Features/ pages that haven't seen an update in say more than a year? Or
> at least mark them as obsolete somehow?
Plenty of them are marked as complete or obsolete:
https://wiki.qemu.org/Category:Completed_feature_pages
https://wiki.qemu.org/Category:Obsolete_feature_pages
Last time I cleaned them up, I couldn't quite decide if some were
completed or obsolete, and QAPI is one of them.
Paolo
next prev parent reply other threads:[~2017-12-15 18:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 18:15 [Qemu-devel] [PATCH v1 0/2] QMP: implementing qmp_cpu Daniel Henrique Barboza
2017-12-13 18:15 ` [Qemu-devel] [PATCH v1 1/2] qmp.c: (re)implement qmp_cpu Daniel Henrique Barboza
2017-12-14 2:18 ` Eric Blake
2017-12-14 15:21 ` Markus Armbruster
2017-12-14 19:46 ` Daniel Henrique Barboza
2017-12-15 13:56 ` Markus Armbruster
2017-12-15 18:11 ` Paolo Bonzini [this message]
2017-12-18 9:20 ` Markus Armbruster
2017-12-15 18:59 ` Dr. David Alan Gilbert
2017-12-18 9:12 ` Markus Armbruster
2017-12-13 18:15 ` [Qemu-devel] [PATCH v1 2/2] cpus.c: change qmp_query_cpus 'value->current' logic Daniel Henrique Barboza
2017-12-14 19:50 ` Daniel Henrique Barboza
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=bf9ded69-6cf6-f7bf-cfca-a31a6b784211@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=danielhb@linux.vnet.ibm.com \
--cc=dgilbert@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.