Subject: Re: bug#53207: 28.0.91; create-lockfiles nil breaks file change detection

From: Lars Ingebrigtsen <[email-masked]>
Date: Sat, 15 Jan 2022 09:06:17 +0100

Glenn Morris <[email-masked]> writes:

> Was it functionally necessary for the addition of lock file transforms
> to break the create-lockfiles nil case? If not, why isn't restoring the
> functionality being considered?

Oh, is this a fallout from introducing `lock-file-name-transforms'?
Then changing the semantics of `create-lockfiles' was not intended, and
the previous semantics should be restored.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no