unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Brian Cully via "Emacs development discussions." <emacs-devel@gnu.org>
Cc: Brian Cully <bjc@spork.org>
Subject: Re: [ELPA] new package: tramp-docker
Date: Mon, 03 Oct 2022 19:52:11 +0200	[thread overview]
Message-ID: <87k05gokvo.fsf@gmx.de> (raw)
In-Reply-To: <77917a56-7bce-d52c-122f-f9273d678896@spork.org> (Brian Cully via's message of "Mon, 3 Oct 2022 09:45:43 -0400")

Brian Cully via "Emacs development discussions." <emacs-devel@gnu.org>
writes:

> On 10/3/22 09:03, Philippe Vaucher wrote:
>> So, if I understand correctly tramp-docker is a rewrite of
>> docker-tramp just so it can be included in ELPA?
>
> This is correct. Although it has now been moved into Tramp directly so
> it will be included in Emacs 29.1.

... and back in GNU ELPA for the goodness of older Emacs versions, once
Tramp 2.6 has been released.

> -bjc

Best regards, Michael.



  reply	other threads:[~2022-10-03 17:52 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bf072225-5933-aef0-6fed-4da031311766@spork.org>
2022-10-03 13:45 ` [ELPA] new package: tramp-docker Brian Cully via Emacs development discussions.
2022-10-03 17:52   ` Michael Albinus [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2022-09-23 15:58 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-24  2:44 ` Richard Stallman
2022-09-24  5:53   ` 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

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=87k05gokvo.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --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).