unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Brian Cully via "Emacs development discussions." <emacs-devel@gnu.org>
To: Michael Albinus <Michael.Albinus@gmx.de>
Cc: miha@kamnitnik.top, Brian Cully <bjc@kublai.com>, emacs-devel@gnu.org
Subject: Re: master 152c7322c1: * lisp/net/tramp-docker.el: New file.
Date: Tue, 4 Oct 2022 13:43:02 -0400	[thread overview]
Message-ID: <0a9db7d1-9bc2-50de-797a-3c53630db848@spork.org> (raw)
In-Reply-To: <87h70jmsoh.fsf@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 253 bytes --]

On 10/4/22 12:58, Michael Albinus wrote:
> Could you pls send also some few words about podman for tramp.texi?

This is just a copy of the Docker docs, but s/docker/podman/. I'm not 
really all that familiar with texinfo, so I hope this is okay.

-bjc


[-- Attachment #2: 0001-Add-method-description-for-podman.patch --]
[-- Type: text/x-patch, Size: 1008 bytes --]

From 033128397bdc6ee0b9d9d85c008e823b9d9395aa Mon Sep 17 00:00:00 2001
From: Brian Cully <bjc@kublai.com>
Date: Tue, 4 Oct 2022 13:37:54 -0400
Subject: [PATCH] Add method description for podman.

* tramp.texi (Inline methods): describe podman method.
---
 texi/tramp.texi | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/texi/tramp.texi b/texi/tramp.texi
index 5cb2cf80..94bf446e 100644
--- a/texi/tramp.texi
+++ b/texi/tramp.texi
@@ -912,6 +912,15 @@ Integration for Docker containers.  A container is accessed via
 @samp{user} is the (optional) user that you want to use, and
 @samp{container} is the id or name of the container.
 
+@item @option{podman}
+@cindex method @option{podman}
+@cindex @option{podman} method
+
+Integration for Podman containers.  A container is accessed via
+@file{@trampfn{podman,user@@container,/path/to/file}}, where
+@samp{user} is the (optional) user that you want to use, and
+@samp{container} is the id or name of the container.
+
 @end table
 
 
-- 
2.37.3


  reply	other threads:[~2022-10-04 17:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29 16:50 master 152c7322c1: * lisp/net/tramp-docker.el: New file miha
2022-09-29 17:28 ` Michael Albinus
2022-10-03 13:44   ` Brian Cully via Emacs development discussions.
2022-10-03 17:37     ` Michael Albinus
2022-10-04 15:32       ` Brian Cully via Emacs development discussions.
2022-10-04 16:58         ` Michael Albinus
2022-10-04 17:43           ` Brian Cully via Emacs development discussions. [this message]
2022-10-04 18:00             ` Michael Albinus
2022-10-04 18:17               ` Brian Cully via Emacs development discussions.
2022-10-04 18:20                 ` Michael Albinus
2022-10-04 18:33                   ` Brian Cully via Emacs development discussions.
2022-10-04 18:36                     ` Michael Albinus
2022-10-04 18:45                       ` Brian Cully via Emacs development discussions.
2022-10-04 19:21                         ` Michael Albinus

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=0a9db7d1-9bc2-50de-797a-3c53630db848@spork.org \
    --to=emacs-devel@gnu.org \
    --cc=Michael.Albinus@gmx.de \
    --cc=bjc@kublai.com \
    --cc=bjc@spork.org \
    --cc=miha@kamnitnik.top \
    /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).