Subject: bug#49261: 28.0.50; File Locking Breaks Presumptuous Toolchains

From: Eli Zaretskii <[email-masked]>
Date: Thu, 01 Jul 2021 21:31:57 +0300

> From: Michael Albinus <[email-masked]>
> Date: Thu, 01 Jul 2021 18:57:12 +0200
> Cc: Mallchad Skeghyeph <[email-masked]>, [email-masked]
> 
> So the very recommended default lock file name shall be what we have
> now. We could give the user a configuration variable to change this
> behaviour, but with explicit warning about consequences.

I think this was indeed the intent.  There's no intent to change the
default behavior wrt where the lock file is written, only to introduce
a new opt-in behavior.