From: David Vrabel <david.vrabel@citrix.com>
To: George Dunlap <george.dunlap@citrix.com>, xen-devel@lists.xenproject.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Tim Deegan <tim@xen.org>, Jan Beulich <jbeulich@suse.com>,
Ian Jackson <ian.jackson@citrix.com>
Subject: Re: [PATCH] CODING_STYLE: Allow single-sentence comments without full stops
Date: Thu, 4 Aug 2016 11:04:14 +0100 [thread overview]
Message-ID: <57A3131E.5050101@citrix.com> (raw)
In-Reply-To: <1470303456-13210-1-git-send-email-george.dunlap@citrix.com>
On 04/08/16 10:37, George Dunlap wrote:
> One of the common ways in which contributors trip up over the
> CODING_STYLE guides is by not putting a full stop at the end of a
> comment when there is only a single sentence. Calling these out is a
> waste of everybody's time: The full stop at the end of a comment with
> a single sentence (or a single phrase) adds absolutely nothing to the
> legibility of the code.
>
> Modify CODING_STYLE to allow comments with a single sentence or
> sentence fragment to either have a full stop or not, while making it
> clear that comments with multiple sentences must have a full stop at
> the end of each sentence.
>
> Signed-off-by: George Dunlap <george.dunlap@citrix.com>
> ---
> CC: Andrew Cooper <andrew.cooper3@citrix.com>
> CC: Ian Jackson <ian.jackson@citrix.com>
> CC: Jan Beulich <jbeulich@suse.com>
> CC: Konrad Wilk <konrad.wilk@oracle.com>
> CC: Stefano Stabellini <sstabellini@kernel.org>
> CC: Tim Deegan <tim@xen.org>
> CC: Wei Liu <wei.liu2@citrix.com>
> ---
> CODING_STYLE | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/CODING_STYLE b/CODING_STYLE
> index 95842e3..4c3b53a 100644
> --- a/CODING_STYLE
> +++ b/CODING_STYLE
> @@ -93,7 +93,9 @@ Comments
>
> Only C style /* ... */ comments are to be used. C++ style // comments
> should not be used. Multi-word comments should begin with a capital
> -letter and end with a full stop.
> +letter. Comments containing a single sentence may end with a full
> +stop; comments containing several sentences must have a full stop
> +after each sentence.
I would suggest a coding style that specifies the useful properties of a
comment and not call out some irrelevant, minor grammar point.
So, I think this should be.
"Comments should be clear and understandable."
Reviewers should be advised to not nit-pick grammar or spelling issues
in comments unless they harm clarity or readability.
Committers who particularly care should be prepared to fix any minor
grammar or spelling issues when committing.
David
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-08-04 10:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 9:37 [PATCH] CODING_STYLE: Allow single-sentence comments without full stops George Dunlap
2016-08-04 9:46 ` George Dunlap
2016-08-04 9:49 ` George Dunlap
2016-08-04 10:04 ` David Vrabel [this message]
2016-08-04 10:38 ` George Dunlap
2016-08-04 10:09 ` Jan Beulich
2016-08-04 10:11 ` George Dunlap
2016-08-04 10:25 ` Ian Jackson
2016-08-05 13:56 ` George Dunlap
2016-08-08 10:10 ` George Dunlap
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=57A3131E.5050101@citrix.com \
--to=david.vrabel@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=jbeulich@suse.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@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.