From: Jeronimo Pellegrini 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: 35639@debbugs.gnu.org, Jeronimo Pellegrini <j_p@aleph0.info>
Subject: bug#35639: 27.0.50; tramp fails to use ssh on LibreCMC (no base64 encoder available, and not mentioned in tramp manual)
Date: Sat, 11 Jan 2020 10:07:28 -0300 [thread overview]
Message-ID: <20200111130728.GA1641575@socrates.lan> (raw)
In-Reply-To: <875zhkpz0d.fsf@gmx.de>
On Thu, Jan 09, 2020 at 01:58:42PM +0100, Michael Albinus wrote:
> Hi Jeronimo,
Hello Michael!
>
> I've committed the appended patch to the Emacs and Tramp git
> repositories. Could you, pls, test with your LibeCMC machine?
Yes -- however, I am travelling, and will only be back on the 15th
of January, and until then I won't have access to that mahine.
Is that ok?
> If you don't use the git repositories, you might install Tramp 2.4.3
> from GNU ELPA, and apply the patch on top of it.
I use Emacs from the git repository -- I suppose it already contains
the patch?
J.
next prev parent reply other threads:[~2020-01-11 13:07 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 16:25 bug#35639: 27.0.50; tramp fails to use ssh on LibreCMC (no base64 encoder available, and not mentioned in tramp manual) Jeronimo Pellegrini
2019-05-08 18:29 ` Michael Albinus
2019-05-08 23:01 ` Jeronimo Pellegrini
2019-05-09 7:35 ` Michael Albinus
2019-05-09 10:19 ` Jeronimo Pellegrini
2019-05-09 12:05 ` Michael Albinus
2019-05-09 12:37 ` Jeronimo Pellegrini
2019-05-09 12:45 ` Michael Albinus
2019-05-09 19:52 ` Jeronimo Pellegrini
2019-05-09 20:02 ` Michael Albinus
2019-05-09 20:11 ` Jeronimo Pellegrini
2019-05-10 8:40 ` Michael Albinus
2019-05-10 9:07 ` Robert Pluim
2019-05-10 9:17 ` Michael Albinus
2019-05-10 9:49 ` Jeronimo Pellegrini
2019-05-10 10:18 ` Michael Albinus
2019-05-10 14:45 ` Jeronimo Pellegrini
2019-05-11 1:57 ` Jeronimo Pellegrini
2019-05-12 8:43 ` Michael Albinus
2019-05-17 19:00 ` Jeronimo Pellegrini
2019-05-18 7:46 ` Michael Albinus
2019-10-11 13:14 ` Michael Albinus
2019-10-14 1:50 ` Jeronimo Pellegrini via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-10-14 7:59 ` Michael Albinus
2019-12-27 17:26 ` Michael Albinus
2019-12-27 18:42 ` Eli Zaretskii
2019-12-30 13:12 ` Jeronimo Pellegrini
2020-01-01 9:28 ` Michael Albinus
2020-01-01 15:39 ` Jeronimo Pellegrini via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-01-09 12:58 ` Michael Albinus
2020-01-11 13:07 ` Jeronimo Pellegrini via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2020-01-11 13:23 ` Michael Albinus
2020-01-16 20:09 ` Jeronimo Pellegrini via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-01-16 20:23 ` Michael Albinus
2019-10-15 2:38 ` Richard Stallman
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=20200111130728.GA1641575@socrates.lan \
--to=bug-gnu-emacs@gnu.org \
--cc=35639@debbugs.gnu.org \
--cc=j_p@aleph0.info \
--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).