From: Eli Zaretskii <eliz@gnu.org>
To: Takesi Ayanokoji <ayanokoji.takesi@gmail.com>
Cc: 52059-done@debbugs.gnu.org
Subject: bug#52059: typos in Emacs documentations
Date: Tue, 23 Nov 2021 16:39:06 +0200 [thread overview]
Message-ID: <83v90jndh1.fsf@gnu.org> (raw)
In-Reply-To: <CAN7WbiZHFWXmwBxR0qQGuQN5k99V4JvJCXBOOMjCp2AD_98rQQ@mail.gmail.com> (message from Takesi Ayanokoji on Tue, 23 Nov 2021 23:30:23 +0900)
> From: Takesi Ayanokoji <ayanokoji.takesi@gmail.com>
> Date: Tue, 23 Nov 2021 23:30:23 +0900
>
> I found some typos in efaq.texi and anti.texi.
>
> Please see attached patch.
Thanks, installed on the release branch.
prev parent reply other threads:[~2021-11-23 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 14:30 bug#52059: typos in Emacs documentations Takesi Ayanokoji
2021-11-23 14:39 ` Eli Zaretskii [this message]
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=83v90jndh1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=52059-done@debbugs.gnu.org \
--cc=ayanokoji.takesi@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).