From: Juergen Gross <jgross@suse.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>, xen-devel@lists.xenproject.org
Cc: Lars Kurth <lars.kurth@citrix.com>,
George Dunlap <george.dunlap@citrix.com>
Subject: Re: [PATCH 0/5] SUPPORT.md: Distinguish descriptions from caveats
Date: Fri, 13 Apr 2018 06:37:21 +0200 [thread overview]
Message-ID: <fb5d6117-68b4-e7f5-278d-e835f2a51731@suse.com> (raw)
In-Reply-To: <1523557603-22218-1-git-send-email-ian.jackson@eu.citrix.com>
On 12/04/18 20:26, Ian Jackson wrote:
> The new support matrix output puts a [*] after each entry in the
> support matrix in many cases where the linked-to text is simply a
> longer description of the feature.
>
> Remedy this by distinguishing text which expands on a feature
> description from text which qualifies its support status.
>
> There are 3 patches to processing machinery, followed by two patches
> to SUPPORT.md - one to make the distinction, throughout, and one to
> document it.
>
> The patches to SUPPORT.md would ideally go to 4.10 too.
>
> 1/5 docs/parse-support-md: internals: Introduce docref_a
> 2/5 docs/parse-support-md: internals: Rename HasText to
> 3/5 SUPPORT.md, support matrix: Treat commentary before
> 4/5 SUPPORT.md: Move descriptions up before Status info
> 5/5 SUPPORT.md: Document the new text ordering rule
For the complete series:
Release-acked-by: Juergen Gross <jgross@suse.com>
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-04-13 4:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 18:26 [PATCH 0/5] SUPPORT.md: Distinguish descriptions from caveats Ian Jackson
2018-04-12 18:26 ` [PATCH 1/5] docs/parse-support-md: internals: Introduce docref_a Ian Jackson
2018-04-12 18:26 ` [PATCH 2/5] docs/parse-support-md: internals: Rename HasText to HasCaveat Ian Jackson
2018-04-12 18:26 ` [PATCH 3/5] SUPPORT.md, support matrix: Treat commentary before status as description Ian Jackson
2018-04-12 18:26 ` [PATCH 4/5] SUPPORT.md: Move descriptions up before Status info Ian Jackson
2018-04-13 11:31 ` Lars Kurth
2018-04-17 13:22 ` Ian Jackson
2018-04-17 15:49 ` Lars Kurth
2018-04-12 18:26 ` [PATCH 5/5] SUPPORT.md: Document the new text ordering rule Ian Jackson
2018-04-13 10:14 ` Lars Kurth
2018-04-13 10:31 ` Ian Jackson
2018-04-13 11:58 ` Lars Kurth
2018-04-12 18:29 ` [PATCH 0/5] SUPPORT.md: Distinguish descriptions from caveats Ian Jackson
2018-04-13 7:56 ` Lars Kurth
2018-04-13 4:37 ` Juergen Gross [this message]
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=fb5d6117-68b4-e7f5-278d-e835f2a51731@suse.com \
--to=jgross@suse.com \
--cc=george.dunlap@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=lars.kurth@citrix.com \
--cc=xen-devel@lists.xenproject.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.