From: Richard Stallman <rms@gnu.org>
To: Brian Cully <bjc@spork.org>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] new package: tramp-docker
Date: Fri, 23 Sep 2022 22:44:31 -0400 [thread overview]
Message-ID: <E1obv9b-0001kH-ES@fencepost.gnu.org> (raw)
In-Reply-To: <5674f36a-c276-fd77-b4d2-1525c75a1602@spork.org> (emacs-devel@gnu.org)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
Could you tell me a bit more about what it means for Tramp to "use
Docker containers" as the remote environment?
As I recall, Tramp connects to another computer using a standard
protocol and transmits files that way. Doing this, Tramp would not
know how the other machine implements the protocol. For instance, if
it used ftp (in the past), how that machine runs an ftp server was not
Tramp's concern. Likewise if it uses http.
Thus, Tramp would neither know nor care whether the service is
implemented with a container.
Why then does Tramp need amy special code for the case where
that service is implemented with a container?
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2022-09-24 2:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 15:58 [ELPA] new package: tramp-docker Brian Cully via Emacs development discussions.
2022-09-23 16:19 ` Philip Kaludercic
2022-09-23 17:47 ` Michael Albinus
[not found] ` <63d5f29a-05ed-f8c5-796c-a6eb9e28d575@spork.org>
2022-09-23 18:00 ` Michael Albinus
2022-09-23 18:09 ` Michael Albinus
2022-09-24 10:34 ` Michael Albinus
[not found] ` <44bd6537-316c-acc7-a4d6-6123bc32e2c0@spork.org>
2022-09-24 16:56 ` Michael Albinus
2022-09-24 17:31 ` Brian Cully via Emacs development discussions.
2022-09-27 16:54 ` Michael Albinus
2022-09-24 2:44 ` Richard Stallman [this message]
2022-09-24 5:53 ` [ELPA] " Robin Tarsiger
2022-09-24 10:45 ` Michael Albinus
2022-10-06 22:03 ` Richard Stallman
2022-10-07 7:35 ` Philip Kaludercic
2022-10-08 22:34 ` Richard Stallman
2022-10-09 11:54 ` Philip Kaludercic
2022-10-15 20:43 ` Richard Stallman
2022-10-15 20:43 ` Richard Stallman
2022-10-16 13:33 ` Philip Kaludercic
2022-10-17 12:30 ` zimoun
2022-10-19 17:02 ` Richard Stallman
2022-10-20 8:18 ` zimoun
2022-10-22 20:03 ` Richard Stallman
2022-10-15 20:43 ` Richard Stallman
2022-10-10 13:55 ` Brian Cully via Emacs development discussions.
2022-10-10 17:46 ` zimoun
2022-10-03 13:03 ` Philippe Vaucher
[not found] <bf072225-5933-aef0-6fed-4da031311766@spork.org>
2022-10-03 13:45 ` Brian Cully via Emacs development discussions.
2022-10-03 17:52 ` Michael Albinus
-- strict thread matches above, loose matches on Subject: below --
2022-10-16 4:46 Payas Relekar
2022-10-18 12:06 ` Richard Stallman
2022-10-18 9:11 ` Payas Relekar
2022-10-20 19:45 ` Richard Stallman
2022-10-21 11:35 ` Payas Relekar
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=E1obv9b-0001kH-ES@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=bjc@spork.org \
--cc=emacs-devel@gnu.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 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).