From: Bart Van Assche <bvanassche@acm.org>
To: Federico Vaga <federico.vaga@vaga.pv.it>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Matthew Wilcox <willy@infradead.org>,
"Geyslan G . Bem" <geyslan@gmail.com>,
Tiago Natel de Moura <tiago4orion@gmail.com>,
Alison Chaiken <alison@she-devel.com>,
Joe Perches <joe@perches.com>, Li Yang <leo@zh-kernel.org>
Subject: Re: [PATCH] Documentation/CodingStyle: Use directory-local variables for emacs
Date: Fri, 04 Jan 2019 14:39:10 -0800 [thread overview]
Message-ID: <1546641550.83374.8.camel@acm.org> (raw)
In-Reply-To: <1951386.HLNclI27qt@harkonnen>
On Fri, 2019-01-04 at 23:10 +0100, Federico Vaga wrote:
> On Friday, January 4, 2019 10:08:33 PM CET Bart Van Assche 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: Geyslan G. Bem <geyslan@gmail.com>
> > Cc: Tiago Natel de Moura <tiago4orion@gmail.com>
> > Cc: Alison Chaiken <alison@she-devel.com>
> > Cc: Joe Perches <joe@perches.com>
> > Cc: Federico Vaga <federico.vaga@vaga.pv.it>
> > Cc: Li Yang <leo@zh-kernel.org>
> > ---
> > Documentation/process/coding-style.rst | 57 +++++++++++++++++---------
> > 1 file changed, 37 insertions(+), 20 deletions(-)
> >
> > Changes compared to v1:
> > - Removed top-level .dir-locals.el file again and updated coding-style.rst
> > instead. - Restored the humourous paragraph about emacs.
> > - Left out Italian and Chinese translations.
>
> Since now there are only code changes, I think you can apply them on both
> Italian and Chinese translations.
Good point.
> As a general comment, I personally think that it worth to mention the fact
> that the user can take this code (actually part of it) and put it in a .dir-
> locals.el file in the top-level directory.
I'm not sure we should recommend this. Settings in ~/.emacs are not affected
by git clean -f -x but .dir-locals.el is removed by that command.
Thanks,
Bart.
next prev parent reply other threads:[~2019-01-04 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 21:08 [PATCH] Documentation/CodingStyle: Use directory-local variables for emacs Bart Van Assche
2019-01-04 21:08 ` [PATCH] Documentation/CodingStyle: Move emacs settings into .dir-locals.el Bart Van Assche
2019-01-04 21:11 ` Bart Van Assche
2019-01-04 22:10 ` [PATCH] Documentation/CodingStyle: Use directory-local variables for emacs Federico Vaga
2019-01-04 22:39 ` Bart Van Assche [this message]
2019-01-05 19:58 ` Alison Chaiken
2019-01-05 21:04 ` Bart Van Assche
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=1546641550.83374.8.camel@acm.org \
--to=bvanassche@acm.org \
--cc=alison@she-devel.com \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=geyslan@gmail.com \
--cc=joe@perches.com \
--cc=leo@zh-kernel.org \
--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).