From: Cornelia Huck <cohuck@redhat.com>
To: Yanan Wang <wangyanan55@huawei.com>,
qemu-devel@nongnu.org, libvir-list@redhat.com
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Andrew Jones" <drjones@redhat.com>,
"Yanan Wang" <wangyanan55@huawei.com>,
wanghaibin.wang@huawei.com
Subject: Re: [PATCH 2/2] docs/about: Unify the subject format
Date: Fri, 20 Aug 2021 12:18:06 +0200 [thread overview]
Message-ID: <87zgtcqv1d.fsf@redhat.com> (raw)
In-Reply-To: <20210820015628.173532-3-wangyanan55@huawei.com>
On Fri, Aug 20 2021, Yanan Wang <wangyanan55@huawei.com> wrote:
> Unify the subject format in deprecated.rst to "since X.Y".
> Unify the subject format in removed-features.rst to "removed in X.Y".
It seems unlikely that we will ever deprecate something in a stable
release, and even more unlikely that we'll remove something in one, so
the short versions look like the thing we want to standardize on.
>
> Signed-off-by: Yanan Wang <wangyanan55@huawei.com>
> ---
> docs/about/deprecated.rst | 56 ++++++++++++++++-----------------
> docs/about/removed-features.rst | 28 ++++++++---------
> 2 files changed, 42 insertions(+), 42 deletions(-)
Unrelated to your patch, line 143 in removed-features.rst reads
``-vnc ...,tls=...``, ``-vnc ...,x509=...`` & ``-vnc ...,x509verify=...``
and is missing the release it was removed in (presumably 3.1?)
Anyway,
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2021-08-20 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 1:56 [PATCH 0/2] docs/about: some documentation clean-up Yanan Wang
2021-08-20 1:56 ` [PATCH 1/2] docs/about: Remove the duplicated doc Yanan Wang
2021-08-20 1:56 ` [PATCH 2/2] docs/about: Unify the subject format Yanan Wang
2021-08-20 10:18 ` Cornelia Huck [this message]
2021-08-23 1:34 ` wangyanan (Y)
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=87zgtcqv1d.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=berrange@redhat.com \
--cc=drjones@redhat.com \
--cc=libvir-list@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wanghaibin.wang@huawei.com \
--cc=wangyanan55@huawei.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).