From: Joe Perches <joe@perches.com>
To: Jonathan Corbet <corbet@lwn.net>, LKML <linux-kernel@vger.kernel.org>
Cc: linux-doc@vger.kernel.org, Jean Delvare <jdelvare@suse.de>,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [PATCH] docs: Remove space-before-label guidance from CodingStyle
Date: Wed, 21 Sep 2016 15:43:17 -0700 [thread overview]
Message-ID: <1474497797.15981.7.camel@perches.com> (raw)
In-Reply-To: <20160921155401.7acd5a47@lwn.net>
On Wed, 2016-09-21 at 15:54 -0600, Jonathan Corbet wrote:
> Recent discussion has made it clear that there is no community consensus
> on this particular rule. Remove it now, lest it inspire yet another set
> of unwanted "cleanup" patches.
Thanks. I believe it's better to remove this one too.
next prev parent reply other threads:[~2016-09-21 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 21:54 [PATCH] docs: Remove space-before-label guidance from CodingStyle Jonathan Corbet
2016-09-21 22:43 ` Joe Perches [this message]
2016-09-22 9:27 ` Jean Delvare
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=1474497797.15981.7.camel@perches.com \
--to=joe@perches.com \
--cc=borntraeger@de.ibm.com \
--cc=corbet@lwn.net \
--cc=jdelvare@suse.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.