From: Phil Sung <psung@mit.edu>
To: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: Updating the tour for Xft
Date: Mon, 24 Aug 2009 23:36:32 -0700 [thread overview]
Message-ID: <60c603510908242336p16e5da79ucf89345dfad59c@mail.gmail.com> (raw)
In-Reply-To: <tl7hbwtisgl.fsf@m17n.org>
On Thu, Jul 30, 2009 at 17:52, Kenichi Handa<handa@m17n.org> wrote:
> In article <60c603510907301026i540ba1fbuf14416c17e7bb7cd@mail.gmail.com>, Phil Sung <psung@mit.edu> writes:
> Please consider adding the attached image (showing the HELLO
> file).
Thanks! I included a similar image.
Phil
next prev parent reply other threads:[~2009-08-25 6:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 11:13 Updating the tour for Xft David House
2009-07-30 17:26 ` Phil Sung
[not found] ` <tl7hbwtisgl.fsf@m17n.org>
2009-08-25 6:36 ` Phil Sung [this message]
2009-07-30 17:50 ` Stefan Monnier
2009-07-31 17:54 ` Gilaras Drakeson
2009-08-25 6:32 ` Phil Sung
2009-08-25 7:19 ` Glenn Morris
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=60c603510908242336p16e5da79ucf89345dfad59c@mail.gmail.com \
--to=psung@mit.edu \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
/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).