From: Eli Zaretskii <eliz@gnu.org>
To: fxiny <wtimew@libero.it>, Kenichi Handa <handa@gnu.org>
Cc: 23363@debbugs.gnu.org
Subject: bug#23363: bug fonts display overlap all versions ERRATA CORIGE
Date: Sun, 24 Apr 2016 22:24:40 +0300 [thread overview]
Message-ID: <83d1pe4xon.fsf@gnu.org> (raw)
In-Reply-To: <1837320787.9760711461500001446.JavaMail.httpd@webmail-13.iol.local> (message from fxiny on Sun, 24 Apr 2016 14:13:21 +0200 (CEST))
> Date: Sun, 24 Apr 2016 14:13:21 +0200 (CEST)
> From: fxiny <wtimew@libero.it>
>
> please read "monaco" instead pf "menlo"
> sorry about that
For Handa-san's information.
prev parent reply other threads:[~2016-04-24 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-24 12:13 bug#23363: bug fonts display overlap all versions ERRATA CORIGE fxiny
2016-04-24 19:24 ` 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=83d1pe4xon.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23363@debbugs.gnu.org \
--cc=handa@gnu.org \
--cc=wtimew@libero.it \
/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).