From: Michael Albinus <michael.albinus@gmx.de>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 45691-done@debbugs.gnu.org, uyennhi.qm@gmail.com
Subject: bug#45691: 28.0.50; dired-do-copy leaks metadata in remote Dired buffers
Date: Sun, 10 Jan 2021 17:09:37 +0100 [thread overview]
Message-ID: <87a6tg7ozi.fsf@gmx.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2101101642570.15806@calancha-pc.dy.bbexcite.jp> (Tino Calancha's message of "Sun, 10 Jan 2021 16:43:48 +0100 (CET)")
Tino Calancha <tino.calancha@gmail.com> writes:
Hi Tino,
> I confirm that it is working fine now.
Thanks for the feedback, I'm closing the bug.
> Thank you Michael!
Best regards, Michael.
prev parent reply other threads:[~2021-01-10 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 14:45 bug#45691: 28.0.50; dired-do-copy leaks metadata in remote Dired buffers Tino Calancha
2021-01-10 12:29 ` Michael Albinus
2021-01-10 15:43 ` Tino Calancha
2021-01-10 16:09 ` Michael Albinus [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6tg7ozi.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=45691-done@debbugs.gnu.org \
--cc=tino.calancha@gmail.com \
--cc=uyennhi.qm@gmail.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).