unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: dgbulk@gmail.com, 72450@debbugs.gnu.org
Subject: bug#72450: 29.1; Tramp Failed to Parse OS Name and Version for Windows 11
Date: Sun, 04 Aug 2024 14:01:04 +0300	[thread overview]
Message-ID: <861q34sgb3.fsf@gnu.org> (raw)
In-Reply-To: <877ccwk142.fsf@gmx.de> (message from Michael Albinus on Sun, 04 Aug 2024 12:56:29 +0200)

> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: dgbulk@gmail.com,  72450@debbugs.gnu.org
> Date: Sun, 04 Aug 2024 12:56:29 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > So I guess accessing Windows via ssh is not really supported, and the
> > OP should be advised to use "smb" instead?
> 
> It's preferable, yes. But I would wait for his comment, before we close
> this bug.

Sure, I didn't mean to suggest that we close this bug right away.





  reply	other threads:[~2024-08-04 11:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-03 19:54 bug#72450: 29.1; Tramp Failed to Parse OS Name and Version for Windows 11 Duncan Greatwood
2024-08-04  4:41 ` Eli Zaretskii
2024-08-04  8:28   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-04  9:15     ` Eli Zaretskii
2024-08-04 10:37       ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-04 10:45         ` Eli Zaretskii
2024-08-04 10:56           ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-04 11:01             ` Eli Zaretskii [this message]
2024-08-05  3:39               ` Duncan Greatwood
2024-08-05  8:27                 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]                   ` <mvmcymnfjcc.fsf@suse.de>
2024-08-05 11:56                     ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-05 22:14                   ` Duncan Greatwood
2024-08-06  7:40                     ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-07 21:46                       ` Duncan Greatwood
2024-08-08  5:20                         ` Eli Zaretskii
2024-08-08 11:06                           ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-08 11:11                             ` Eli Zaretskii
2024-08-08 11:18                               ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-08 11:11                         ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-08 18:28                   ` Jim Porter
2024-08-08 19:03                     ` Duncan Greatwood
2024-08-10 10:34                     ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=861q34sgb3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=72450@debbugs.gnu.org \
    --cc=dgbulk@gmail.com \
    --cc=michael.albinus@gmx.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).