From: Michael Albinus <michael.albinus@gmx.de>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: 48829-done@debbugs.gnu.org
Subject: bug#48829: 28.0.50; opening files mith /sudo:root@localhost:… fails
Date: Fri, 25 Jun 2021 14:24:29 +0200 [thread overview]
Message-ID: <87zgvep1xe.fsf@gmx.de> (raw)
In-Reply-To: <8735tklky1.fsf@gmx.de> (Michael Albinus's message of "Mon, 14 Jun 2021 13:55:34 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
Hi Arne,
> Is there something else I could do for you? Otherwise, I'd like to close
> the bug.
No further comment, so I'm closing the bug. Feel free to reopen if
there's still a problem.
Best regards, Michael.
prev parent reply other threads:[~2021-06-25 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 11:22 bug#48829: 28.0.50; opening files mith /sudo:root@localhost:… fails Dr. Arne Babenhauserheide
2021-06-06 8:38 ` Michael Albinus
2021-06-14 11:55 ` Michael Albinus
2021-06-25 12:24 ` 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=87zgvep1xe.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=48829-done@debbugs.gnu.org \
--cc=arne_bab@web.de \
/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).