From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, libvir-list@redhat.com, thuth@redhat.com,
cohuck@redhat.com, pkrempa@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/2] qemu-doc: Move appendix "Deprecated features" to its own file
Date: Mon, 16 Jul 2018 10:41:10 +0100 [thread overview]
Message-ID: <20180716094110.GM5616@redhat.com> (raw)
In-Reply-To: <20180716073226.21127-2-armbru@redhat.com>
On Mon, Jul 16, 2018 at 09:32:25AM +0200, Markus Armbruster wrote:
> Consumers of QEMU need to track feature deprecation. Keeping
> deprecation documentation in its own file helps in two small ways:
>
> * You can track changes the easy and obvious way, with git-log.
> Before, you had to resort to more complex gittery like "git-log
> --oneline -L '/@node Deprecated features/,/@node Supported build
> platforms/:qemu-doc.texi'"
>
> * It lets us use MAINTAINERS to copy interested parties on deprecation
> patches, so they can advise or object before they're a done deal.
> The next commit will do that for libvirt.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> qemu-deprecated.texi | 234 ++++++++++++++++++++++++++++++++++++++++++
> qemu-doc.texi | 235 +------------------------------------------
> 2 files changed, 235 insertions(+), 234 deletions(-)
> create mode 100644 qemu-deprecated.texi
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-07-16 9:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 7:32 [Qemu-devel] [PATCH 0/2] Make it easier to track feature deprecation Markus Armbruster
2018-07-16 7:32 ` [Qemu-devel] [PATCH 1/2] qemu-doc: Move appendix "Deprecated features" to its own file Markus Armbruster
2018-07-16 7:50 ` Thomas Huth
2018-07-16 7:54 ` Cornelia Huck
2018-07-16 9:41 ` Daniel P. Berrangé [this message]
2018-07-16 7:32 ` [Qemu-devel] [PATCH 2/2] MAINTAINERS: New section "Incompatible changes", copy libvir-list Markus Armbruster
2018-07-16 7:54 ` Thomas Huth
2018-07-16 8:02 ` Cornelia Huck
2018-07-16 13:46 ` Markus Armbruster
2018-07-16 7:55 ` Cornelia Huck
2018-07-16 9:39 ` Daniel P. Berrangé
2018-07-24 15:59 ` [Qemu-devel] [libvirt] " Eric Blake
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=20180716094110.GM5616@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=cohuck@redhat.com \
--cc=libvir-list@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).