From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
shuguang79@qq.com, 50869-done@debbugs.gnu.org
Subject: bug#50869: 28.0.50; tramp: void-function tramp-file-name-method--cmacro
Date: Sun, 04 Sep 2022 14:03:58 -0400 [thread overview]
Message-ID: <jwvleqzt3u3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <875yi3aw3a.fsf@gmx.de> (Michael Albinus's message of "Sun, 04 Sep 2022 19:27:37 +0200")
> The question remains if we shall fix something else for this bug, or
> whether we can regard it as solved.
I'm still not very happy with the duplication of `cl-defstruct` in the
loaddefs.el, but I think it's now unrelated to this patch (other than
historical accident), so: closing, thanks,
Stefan
next prev parent reply other threads:[~2022-09-04 18:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 15:15 bug#50869: 28.0.50; tramp: void-function tramp-file-name-method--cmacro Shuguang Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-02 16:36 ` Michael Albinus
2022-03-17 14:39 ` Michael Albinus
2022-04-02 21:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-03 15:44 ` Michael Albinus
2022-09-02 18:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 10:07 ` Lars Ingebrigtsen
2022-09-03 19:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-04 14:53 ` Michael Albinus
2022-09-04 16:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-04 17:27 ` Michael Albinus
2022-09-04 18:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-09-02 11:43 ` Lars Ingebrigtsen
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=jwvleqzt3u3.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=50869-done@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael.albinus@gmx.de \
--cc=monnier@iro.umontreal.ca \
--cc=shuguang79@qq.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.