all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Yuri D'Elia <wavexx@thregr.org>
Cc: Eli Zaretskii <eliz@gnu.org>, 62614-done@debbugs.gnu.org
Subject: bug#62614: Tramp attempts to remove lock file with 'remote-file-name-inhibit-locks t
Date: Tue, 04 Apr 2023 09:55:12 +0200	[thread overview]
Message-ID: <87jzysxesf.fsf@gmx.de> (raw)
In-Reply-To: <87edp0zth5.fsf@wavexx.thregr.org> (Yuri D'Elia's message of "Mon, 03 Apr 2023 20:50:09 +0200")

Version: 30.1

Yuri D'Elia <wavexx@thregr.org> writes:

Hi Yuri,

>>> >> How about trying to remove the lock file, but if creation of lock
>>> >> files is disabled, suppressing the warning?
>>> >
>>> > As above.
>>>
>>> See appended patch.
>>
>> LGTM, thanks.
>>
>>> Shall it go to the emacs-29 or master branch?
>>
>> Master, please.
>
> As for this specific bug report, I'd close it as "fixed".
> The spurious warning was definitely my main complaint.

Pushed to master, closing.

Best regards, Michael.





  reply	other threads:[~2023-04-04  7:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-02 13:28 bug#62614: Tramp attempts to remove lock file with 'remote-file-name-inhibit-locks t Yuri D'Elia
2023-04-03  8:35 ` Michael Albinus
2023-04-03  9:19   ` Yuri D'Elia
2023-04-03  9:54     ` Michael Albinus
2023-04-03 10:01       ` Yuri D'Elia
2023-04-03 10:17         ` Yuri D'Elia
2023-04-03 10:30           ` Michael Albinus
2023-04-03 14:54             ` Yuri D'Elia
2023-04-03 16:32               ` Michael Albinus
2023-04-03 16:45                 ` Eli Zaretskii
2023-04-03 18:50                   ` Yuri D'Elia
2023-04-04  7:55                     ` Michael Albinus [this message]
2023-04-03 14:14       ` Eli Zaretskii
2023-04-03 14:10     ` 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=87jzysxesf.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=62614-done@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=wavexx@thregr.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.