all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: sdt@sebyte.me, 46813@debbugs.gnu.org
Subject: bug#46813: 27.0.91; Form `(subdirs . nil)' in .dir-locals.el does not protect subdirectories
Date: Sun, 28 Feb 2021 20:19:55 +0200	[thread overview]
Message-ID: <83sg5g8378.fsf@gnu.org> (raw)
In-Reply-To: <877dmsnwa7.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun,  28 Feb 2021 14:42:40 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 46813@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
> Date: Sun, 28 Feb 2021 14:42:40 +0100
> 
> There were a whole bunch of different bugs in the .dir-locals.el code.
> The relevant commits are 8f0a2c84, 75f6b264 and possibly 117d58ace.
> 
> I think backporting the first two might be possible (they're tiny), but
> I don't think this is actually a regression in Emacs 27 -- this stuff
> didn't work in Emacs 26 either, if I remember correctly.  So I think
> backporting to Emacs 27 would be out of scope, since we're only fixing
> regressions (and really serious bugs) in Emacs 27 at this time.
> 
> But since the first two commits are really small and "obviously correct"
> (ahem), perhaps it's a good idea to do so anyway.  I have no opinion
> here, perhaps Eli has one?  (Added to the CCs.)

I don't object to backporting those two commits to emacs-27, if you
think those fixes are important to have in v27.2.

Thanks.





  reply	other threads:[~2021-02-28 18:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-27 13:59 bug#46813: 27.0.91; Form `(subdirs . nil)' in .dir-locals.el does not protect subdirectories Sebastian Tennant
2021-02-27 14:09 ` Lars Ingebrigtsen
2021-02-27 17:05   ` Sebastian Tennant
2021-02-28 13:42     ` Lars Ingebrigtsen
2021-02-28 18:19       ` Eli Zaretskii [this message]
2021-03-01 12:37         ` Lars Ingebrigtsen

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=83sg5g8378.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=46813@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=sdt@sebyte.me \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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.