From: Lars Kurth <lars.kurth@citrix.com>
To: Ian Jackson <Ian.Jackson@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
George Dunlap <George.Dunlap@citrix.com>
Subject: Re: [PATCH 5/5] SUPPORT.md: Document the new text ordering rule
Date: Fri, 13 Apr 2018 11:58:05 +0000 [thread overview]
Message-ID: <F7DB1BED-A5A4-4F31-8427-D00CF58C1BDE@citrix.com> (raw)
In-Reply-To: <23248.34588.10447.737086@mariner.uk.xensource.com>
On 13/04/2018, 11:31, "Ian Jackson" <ian.jackson@citrix.com> wrote:
Lars Kurth writes ("Re: [PATCH 5/5] SUPPORT.md: Document the new text ordering rule"):
...
> +In each case, descriptions which expand on the name of a feature as
> +provided in the section heading, precede the Status indications.
>
> The following is a little clearer
> s/, descriptions which expand on the name of a feature as provided in the section heading,/, descriptions which describe the feature in the section heading in more detail,/
I used the wording I did because the word "description" is very
elastic, and might well be thought to include things that we intend as
caveats.
I don't mind either way. Just something which sounded odd.
Lars
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-04-13 11:58 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 [this message]
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
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=F7DB1BED-A5A4-4F31-8427-D00CF58C1BDE@citrix.com \
--to=lars.kurth@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=jgross@suse.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.