From: Michael Albinus <michael.albinus@gmx.de>
To: Jim Porter <jporterbugs@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Ok to backport Eshell manual improvements to 29?
Date: Thu, 13 Jul 2023 09:14:04 +0200 [thread overview]
Message-ID: <871qhcjnb7.fsf@gmx.de> (raw)
In-Reply-To: <c40c492b-3908-28b7-8c07-901991b6e5c7@gmail.com> (Jim Porter's message of "Wed, 12 Jul 2023 18:52:03 -0700")
Jim Porter <jporterbugs@gmail.com> writes:
Hi Jim,
> I just pushed a branch - "scratch/backport-eshell-docs-to-29" - that
> backports all the relevant changes to the Eshell manual that are
> currently on master. I've double-checked that the documentation all
> looks right to me (specifically that the 29 branch doesn't mention any
> features only present on master), but before I merge to the 29 branch,
> I wanted to give others the chance to look over the changes too.
>
> I've opted not to squash any of the commits and to add a note to each
> commit message indicating the Git SHA for each master
> commit. Hopefully that will make it easier if anyone needs to look
> back on these commits in the future.
I haven't checked each commit. Just a diff between eshell.texi in master
and scratch/backport-eshell-docs-to-29. One minor nit: in node
Variables, you have deleted "@vindex $INSIDE_EMACS". Pls keep it.
Otherwise, it LGTM.
Best regards, Michael.
next prev parent reply other threads:[~2023-07-13 7:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 1:52 Ok to backport Eshell manual improvements to 29? Jim Porter
2023-07-13 7:14 ` Michael Albinus [this message]
2023-07-13 16:10 ` Jim Porter
2023-07-14 2:26 ` Jim Porter
2023-07-14 7:10 ` Juri Linkov
2023-07-14 7:22 ` Eli Zaretskii
2023-07-14 16:29 ` Jim Porter
2023-07-14 16:52 ` Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qhcjnb7.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=jporterbugs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.