Re: [Xen-devel] [PATCH 0/5] SUPPORT.md: Distinguish descriptions from caveats

2018-04-13 Thread Lars Kurth 


On 12/04/2018, 19:29, "Ian Jackson"  wrote:

Ian Jackson writes ("[PATCH 0/5] SUPPORT.md: Distinguish descriptions from 
caveats"):
> 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.

Example output:
  https://xenbits.xen.org/people/iwj/2018/support-matrix-example-B-v1/t.html

Looks good to me
Lars
 

___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [Xen-devel] [PATCH 0/5] SUPPORT.md: Distinguish descriptions from caveats

2018-04-12 Thread Juergen Gross 
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 


Juergen

___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [Xen-devel] [PATCH 0/5] SUPPORT.md: Distinguish descriptions from caveats

2018-04-12 Thread Ian Jackson 
Ian Jackson writes ("[PATCH 0/5] SUPPORT.md: Distinguish descriptions from 
caveats"):
> 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.

Example output:
  https://xenbits.xen.org/people/iwj/2018/support-matrix-example-B-v1/t.html

Ian.

___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

[Xen-devel] [PATCH 0/5] SUPPORT.md: Distinguish descriptions from caveats

2018-04-12 Thread Ian Jackson 
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

Ian.

___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel