From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>, michael.albinus@gmx.de
Cc: rgm@gnu.org, ejb@ql.org, 53207@debbugs.gnu.org
Subject: bug#53207: 28.0.91; create-lockfiles nil breaks file change detection
Date: Fri, 28 Jan 2022 16:30:29 +0200 [thread overview]
Message-ID: <83h79oc4qi.fsf@gnu.org> (raw)
In-Reply-To: <877dakht8k.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 28 Jan 2022 14:42:19 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: rgm@gnu.org, ejb@ql.org, michael.albinus@gmx.de, 53207@debbugs.gnu.org
> Date: Fri, 28 Jan 2022 14:42:19 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Lars, what shall we do about this bug report? Should we document the
> > current behavior, or should we move the call to
> > userlock--ask-user-about-supersession-threat out of Flock_file? This
> > should be resolved before the next pretest, I think.
>
> I think we should restore the old behaviour, so that setting
> create-lockfiles to nil doesn't break file change detection. I think
> that means that we have to move
> userlock--ask-user-about-supersession-threat out of Flock_file, yes.
Michael, could you please suggest a patch along these lines? The
changeset which moved userlock--ask-user-about-supersession-threat
into Flock_file and put that under the create-lockfiles condition was
your change to support locking remote files.
next prev parent reply other threads:[~2022-01-28 14:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 14:30 bug#53207: 28.0.91; create-lockfiles nil breaks file change detection Jay Berkenbilt
2022-01-12 17:26 ` Eli Zaretskii
2022-01-12 20:07 ` Jay Berkenbilt
2022-01-12 20:45 ` Eli Zaretskii
2022-01-12 21:35 ` Jay Berkenbilt
2022-01-13 6:43 ` Eli Zaretskii
2022-01-13 13:06 ` Jay Berkenbilt
2022-01-12 18:13 ` Glenn Morris
2022-01-12 18:41 ` Philipp Stephani
2022-01-13 10:54 ` Eli Zaretskii
2022-01-13 13:11 ` Jay Berkenbilt
2022-01-13 13:24 ` Philipp Stephani
2022-01-13 14:02 ` Eli Zaretskii
2022-01-13 15:47 ` Jay Berkenbilt
2022-01-14 14:26 ` Michael Albinus
2022-01-14 14:43 ` Eli Zaretskii
2022-01-14 16:11 ` Glenn Morris
2022-01-14 16:44 ` Eli Zaretskii
2022-01-15 8:06 ` Lars Ingebrigtsen
2022-01-15 8:16 ` Lars Ingebrigtsen
2022-01-15 9:23 ` Eli Zaretskii
2022-01-27 17:19 ` Eli Zaretskii
2022-01-28 13:42 ` Lars Ingebrigtsen
2022-01-28 14:30 ` Eli Zaretskii [this message]
2022-01-28 14:56 ` Michael Albinus
2022-01-28 15:16 ` Eli Zaretskii
2022-01-29 10:53 ` Michael Albinus
2022-01-29 10:57 ` Eli Zaretskii
2022-02-03 13:31 ` Michael Albinus
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=83h79oc4qi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53207@debbugs.gnu.org \
--cc=ejb@ql.org \
--cc=larsi@gnus.org \
--cc=michael.albinus@gmx.de \
--cc=rgm@gnu.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.
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.