From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH v2 for-4.6 1/2] docs: Template for feature documents
Date: Tue, 1 Sep 2015 14:45:20 +0100 [thread overview]
Message-ID: <55E5ABF0.7010107@citrix.com> (raw)
In-Reply-To: <1441114918.26292.26.camel@citrix.com>
On 01/09/15 14:41, Ian Campbell wrote:
> On Tue, 2015-08-25 at 11:40 +0100, Andrew Cooper wrote:
>> +A table with an overview of the support status and applicability.
>> +
>> +---------------- ----------------------------------------------------
>> + Status: e.g. **Supported**/**Tech Preview**/**Experimental**
> These should be well defined somewhere and that definition linked to in the
> template. Perhaps this is the "formal support statement document" mentioned
> in the cover mail but which I haven't stumbled over in my (overflowing)
> post vacation INBOX
It is referring to a thread of Lars', which is attempting to nail down
these definitions.
~Andrew
next prev parent reply other threads:[~2015-09-01 13:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 10:40 [RFC v2 for-4.6 0/2] In-tree feature documentation Andrew Cooper
2015-08-25 10:40 ` [PATCH v2 for-4.6 1/2] docs: Template for feature documents Andrew Cooper
2015-09-01 13:41 ` Ian Campbell
2015-09-01 13:45 ` Andrew Cooper [this message]
2015-08-25 10:40 ` [PATCH v2 for-4.6 2/2] docs: Migration feature document Andrew Cooper
2015-08-27 2:15 ` Jim Fehlig
2015-08-27 10:35 ` Andrew Cooper
2015-08-27 2:44 ` [RFC v2 for-4.6 0/2] In-tree feature documentation Jim Fehlig
2015-08-27 10:46 ` Andrew Cooper
2015-08-27 14:52 ` Ian Jackson
2015-08-27 15:39 ` Andrew Cooper
2015-08-27 17:58 ` Ian Jackson
2015-08-27 18:16 ` Andrew Cooper
2015-08-28 17:16 ` Lars Kurth
2015-08-28 17:40 ` Andrew Cooper
2015-08-28 17:48 ` Andrew Cooper
2015-08-28 17:51 ` Lars Kurth
2015-08-28 18:18 ` Andrew Cooper
2015-08-28 18:52 ` Lars Kurth
2015-08-28 19:06 ` Andrew Cooper
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=55E5ABF0.7010107@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=ian.campbell@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 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.