From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, federicotedin@gmail.com
Subject: Re: INSIDE_EMACS and Tramp
Date: Sat, 02 May 2020 18:04:01 +0200 [thread overview]
Message-ID: <87k11uwcge.fsf@gmx.de> (raw)
In-Reply-To: <83ees2s5vy.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 02 May 2020 18:39:29 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Eli, would it be OK to push something like this to master?
>
> You don't need to ask for permission to push to master. Unless
> there's something very controversial or problematic about this change,
> in which case please tell which part.
There's nothing controversial. Maybe the function names could be
better. And documentation is missing; I'll produce some few phrases for
the manual.
If there's no objection, I'll push in a few days.
> Thanks.
Best regards, Michael.
next prev parent reply other threads:[~2020-05-02 16:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200402230535.10490.95720@vcs0.savannah.gnu.org>
[not found] ` <20200402230536.E0A3F20CDD@vcs0.savannah.gnu.org>
2020-04-03 8:35 ` INSIDE_EMACS and Tramp (was: master f28166d: Copy INSIDE_EMACS env variable to subprocesses in Eshell (Bug#25496)) Michael Albinus
2020-04-04 14:53 ` Federico Tedin
2020-04-04 15:10 ` INSIDE_EMACS and Tramp Michael Albinus
2020-04-04 20:13 ` Federico Tedin
2020-04-13 9:07 ` Michael Albinus
2020-04-17 20:16 ` Federico Tedin
2020-05-02 14:54 ` Michael Albinus
2020-05-02 15:39 ` Eli Zaretskii
2020-05-02 16:04 ` Michael Albinus [this message]
2020-05-02 16:17 ` Eli Zaretskii
2020-05-02 16:16 ` Eli Zaretskii
2020-05-02 17:20 ` Stefan Monnier
2020-05-03 12:33 ` Michael Albinus
2020-05-03 14:51 ` Stefan Monnier
2020-05-03 16:08 ` Michael Albinus
2020-05-03 20:54 ` Stefan Monnier
2020-05-04 7:08 ` Michael Albinus
2020-05-04 8:47 ` Michael Albinus
2020-05-04 15:38 ` Stefan Monnier
2020-05-04 16:11 ` Michael Albinus
2020-05-03 14:52 ` Federico Tedin
2020-05-03 16:19 ` 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=87k11uwcge.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=federicotedin@gmail.com \
/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).