From: Jonathan Corbet <corbet@lwn.net>
To: Bart Van Assche <bvanassche@acm.org>
Cc: linux-doc@vger.kernel.org, Matthew Wilcox <willy@infradead.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
Alison Chaiken <alison@she-devel.com>,
Joe Perches <joe@perches.com>,
Federico Vaga <federico.vaga@vaga.pv.it>,
"Geyslan G . Bem" <geyslan@gmail.com>,
Tiago Natel de Moura <tiago4orion@gmail.com>
Subject: Re: [PATCH v3] Documentation/CodingStyle: Use directory-local variables for emacs settings
Date: Mon, 7 Jan 2019 15:34:41 -0700 [thread overview]
Message-ID: <20190107153441.507affc0@lwn.net> (raw)
In-Reply-To: <20190107182019.105393-1-bvanassche@acm.org>
On Mon, 7 Jan 2019 10:20:19 -0800
Bart Van Assche <bvanassche@acm.org> wrote:
> In emacs 23.1 support for directory-local variables was added (see also
> https://lists.gnu.org/archive/html/info-gnu-emacs/2009-07/msg00000.html).
> Simplify the settings in coding-style.rst by using that feature.
> Additionally, do not inherit any settings from emacs' linux coding style
> to minimize dependencies on the version of emacs that is being used.
>
> I have verified with several large and nontrivial kernel source files
> that the new settings format code according to what checkpatch expects.
>
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> Cc: Matthew Wilcox <willy@infradead.org>
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Cc: Alison Chaiken <alison@she-devel.com>
> Cc: Joe Perches <joe@perches.com>
> Cc: Federico Vaga <federico.vaga@vaga.pv.it>
> Cc: Geyslan G. Bem <geyslan@gmail.com>
> Cc: Tiago Natel de Moura <tiago4orion@gmail.com>
I've applied this (and I'm off to change my .emacs file). Thanks!
jon
prev parent reply other threads:[~2019-01-07 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 18:20 [PATCH v3] Documentation/CodingStyle: Use directory-local variables for emacs settings Bart Van Assche
2019-01-07 20:40 ` Joe Perches
2019-01-07 22:34 ` Jonathan Corbet [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=20190107153441.507affc0@lwn.net \
--to=corbet@lwn.net \
--cc=alison@she-devel.com \
--cc=bvanassche@acm.org \
--cc=federico.vaga@vaga.pv.it \
--cc=geyslan@gmail.com \
--cc=jani.nikula@linux.intel.com \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=tiago4orion@gmail.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).