From: Ian Campbell <ian.campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 1/2] docs: Template for feature documents
Date: Mon, 21 Sep 2015 12:53:02 +0100 [thread overview]
Message-ID: <1442836382.10338.56.camel@citrix.com> (raw)
In-Reply-To: <1442325268-12636-2-git-send-email-andrew.cooper3@citrix.com>
On Tue, 2015-09-15 at 14:54 +0100, Andrew Cooper wrote:
> +# Basics
> +
> +A table with an overview of the support status and applicability.
> +
> +---------------- ----------------------------------------------------
> + Status: e.g. **Supported**/**Tech Preview**/**Experimental**
My main concern is still the lack of a precise meaning for these terms.
However this is not a problem with this series per-se and we can always
update the template once we know what they mean.
So I've acked and applied both patches to staging and staging-4.6.
next prev parent reply other threads:[~2015-09-21 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 13:54 [PATCH v3 for-4.6 0/2] In-tree feature documentation Andrew Cooper
2015-09-15 13:54 ` [PATCH 1/2] docs: Template for feature documents Andrew Cooper
2015-09-21 11:53 ` Ian Campbell [this message]
2015-09-15 13:54 ` [PATCH 2/2] docs: Migration feature document Andrew Cooper
2015-09-16 14:37 ` [PATCH v3 for-4.6 0/2] In-tree feature documentation Wei Liu
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=1442836382.10338.56.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.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).