From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
mreitz@redhat.com, qemu-devel@nongnu.org, qemu-block@nongnu.org,
armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH] block: Deprecate bdrv_set_read_only() and users
Date: Wed, 8 Nov 2017 13:16:12 +0100 [thread overview]
Message-ID: <20171108121612.GD30890@localhost.localdomain> (raw)
In-Reply-To: <f5dc8522-86cd-c8fa-2dd7-d9e36c5c8245@redhat.com>
Am 08.11.2017 um 13:00 hat Paolo Bonzini geschrieben:
> On 08/11/2017 12:51, Kevin Wolf wrote:
> > Am 08.11.2017 um 11:49 hat Daniel P. Berrange geschrieben:
> >> On Wed, Nov 08, 2017 at 11:44:01AM +0100, Paolo Bonzini wrote:
> >>> I am not sure this counts as deprecation, but it should go in the
> >>> release notes as "future incompatible changes", and that section
> >>> probably should go in qemu-doc.texi itself.
> >>
> >> Yeah, adding a "Incompatible changes" appendix to the qemu-doc.texi
> >> would be useful, listing the planned change, and when it is actually
> >> made. That way apps adding support for a feature have an indication
> >> of any incompatiblities they might need to care about.
> >
> > You mean a section containing future incompatible changes as well as
> > already implemented incompatible changes?
> >
> > What would we do with the existing "Deprecated features" section? Would
> > it become a subsection of "Incompatible changes"? Or would we just
> > rename it and the subsections would stay on the same level and get
> > "deprecated" added to their title? Or a completely different structure?
> >
> > I'm okay with adding a little documentation in this patch if I know what
> > it should look like, but if it turns into a major overhaul of the
> > documentation on incompatible changes, it's probably out of scope for
> > this patch.
>
> For now I would just add a section to the changelog. That ensures that
> we don't forget and end up doing nothing.
Okay, done. Thanks!
Kevin
next prev parent reply other threads:[~2017-11-08 12:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 17:26 [Qemu-devel] [PATCH] block: Deprecate bdrv_set_read_only() and users Kevin Wolf
2017-11-07 17:39 ` Daniel P. Berrange
2017-11-08 10:44 ` Paolo Bonzini
2017-11-08 10:49 ` Daniel P. Berrange
2017-11-08 11:51 ` Kevin Wolf
2017-11-08 12:00 ` Paolo Bonzini
2017-11-08 12:16 ` Kevin Wolf [this message]
2017-11-08 12:31 ` Daniel P. Berrange
2017-11-07 20:29 ` Eric Blake
2017-11-08 10:04 ` Kevin Wolf
2017-11-08 12:20 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2017-11-08 14:34 ` Eric Blake
2017-11-08 14:33 ` [Qemu-devel] " 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=20171108121612.GD30890@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@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 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.