From: Jani Nikula <jani.nikula@linux.intel.com>
To: Bart Van Assche <bvanassche@acm.org>,
Federico Vaga <federico.vaga@vaga.pv.it>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, "Geyslan G . Bem" <geyslan@gmail.com>,
Tiago Natel de Moura <tiago4orion@gmail.com>,
Alison Chaiken <alison_chaiken@mentor.com>,
Joe Perches <joe@perches.com>, Zhang Le <r0bertz@gentoo.org>,
Li Yang <leo@zh-kernel.org>
Subject: Re: [PATCH] Documentation/CodingStyle: Move emacs settings into .dir-locals.el
Date: Mon, 07 Jan 2019 12:29:02 +0200 [thread overview]
Message-ID: <878szw92xd.fsf@intel.com> (raw)
In-Reply-To: <1546620035.163063.42.camel@acm.org>
On Fri, 04 Jan 2019, Bart Van Assche <bvanassche@acm.org> wrote:
> Regarding users having their own version of .dir-locals.el: why do you
> think anyone would want to do that?
Err, .dir-locals.el is not only for a project to enforce local variables
on emacs users, it's also for the users to set local variables for the
project.
> Anyway, if anyone wants to replace that file they can provide a
> .dir-locals-2.el file.
It does not replace anything, it's loaded in addition to .dir-locals.el.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2019-01-07 10:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 0:39 [PATCH] Documentation/CodingStyle: Move emacs settings into .dir-locals.el Bart Van Assche
2019-01-04 2:12 ` Matthew Wilcox
2019-01-04 16:06 ` Bart Van Assche
2019-01-04 9:44 ` Federico Vaga
2019-01-04 11:18 ` Jani Nikula
2019-01-04 16:40 ` Bart Van Assche
2019-01-07 10:29 ` Jani Nikula [this message]
2019-01-04 16:32 ` Bart Van Assche
2019-01-04 16:41 ` Jonathan Corbet
2019-01-04 18:26 ` Joe Perches
-- strict thread matches above, loose matches on Subject: below --
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
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=878szw92xd.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=alison_chaiken@mentor.com \
--cc=bvanassche@acm.org \
--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=r0bertz@gentoo.org \
--cc=tiago4orion@gmail.com \
/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.