From: Kenichi Handa <handa@m17n.org>
Subject: Re: Dependencies in leim/Makefile.in
Date: Tue, 4 May 2004 10:27:26 +0900 (JST) [thread overview]
Message-ID: <200405040127.KAA13848@etlken.m17n.org> (raw)
I wrote:
> I've just installed the attached fix which takes the
> different approach. I gave up generating a list of TIT and
> MISC-DIC sources, but could eliminate kludgy code for
> avoiding parallel make problems.
and someone (sorry, I lost your mail) reported a bug of that
change. I've just installed a fix.
---
Ken'ichi HANDA
handa@m17n.org
next reply other threads:[~2004-05-04 1:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 1:27 Kenichi Handa [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-26 12:05 Dependencies in leim/Makefile.in Eli Zaretskii
2004-04-29 1:42 ` Kenichi Handa
2004-04-29 5:58 ` Eli Zaretskii
2004-05-01 5:51 ` Kenichi Handa
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=200405040127.KAA13848@etlken.m17n.org \
--to=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).