From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: jsynacek@redhat.com, 24656@debbugs.gnu.org
Subject: bug#24656: 25.1; Emacs leaves lock files on a CIFS share
Date: Wed, 12 Oct 2016 09:40:26 +0300 [thread overview]
Message-ID: <83lgxuax45.fsf@gnu.org> (raw)
In-Reply-To: <3ae887c3-54bd-0a92-2d69-f8aefe18afb1@cs.ucla.edu> (message from Paul Eggert on Tue, 11 Oct 2016 15:46:58 -0700)
> Cc: jsynacek@redhat.com, 24656@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Tue, 11 Oct 2016 15:46:58 -0700
>
> On 10/11/2016 01:58 PM, Eli Zaretskii wrote:
> > Do you see any
> > dangers in the patch that would make it prudent to give this change a
> > longer testing phase than what we will have before 25.2?
>
> No, the variant I installed into master should be pretty safe in that
> regard, as it avoids the interoperability issues inherent in instituting
> a new syntax, and the pattern it's looking for is unlikely to appear in
> scenarios that do not involve Emacs and this buggy file system.
That was my impression as well, so I think it should be backported to
the release branch.
Thanks.
next prev parent reply other threads:[~2016-10-12 6:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 11:30 bug#24656: 25.1; Emacs leaves lock files on a CIFS share Jan Synáček
2016-10-10 12:14 ` Eli Zaretskii
2016-10-10 13:49 ` Jan Synacek
2016-10-10 15:49 ` Eli Zaretskii
2016-10-11 6:32 ` Jan Synacek
2016-10-11 6:49 ` Eli Zaretskii
2016-10-11 6:52 ` Jan Synacek
2016-10-11 15:59 ` Paul Eggert
2016-10-11 16:29 ` Eli Zaretskii
2016-10-11 16:53 ` Paul Eggert
2016-10-11 17:07 ` Eli Zaretskii
2016-10-11 20:15 ` Paul Eggert
2016-10-11 20:58 ` Eli Zaretskii
2016-10-11 22:46 ` Paul Eggert
2016-10-12 6:40 ` Eli Zaretskii [this message]
2016-10-12 16:21 ` Paul Eggert
2016-10-12 16:53 ` Eli Zaretskii
2016-10-11 17:43 ` Achim Gratz
2016-10-11 18:16 ` Eli Zaretskii
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=83lgxuax45.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24656@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=jsynacek@redhat.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.
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.