From: DJ Delorie <dj@delorie.com>
To: pedwards@disaster.jaj.com
Cc: gcc@gcc.gnu.org, binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: libiberty docs are in
Date: Thu, 27 Sep 2001 13:12:00 -0000 [thread overview]
Message-ID: <200109272012.f8RKCCH14283@envy.delorie.com> (raw)
In-Reply-To: <20010927150200.G6776@disaster.jaj.com>
> and I wasn't about to try and run a texinfo file through any of the
> spell checkers I had available to me at the time.
cat libiberty.info* | ispell -l | sort -u
Although it spits out lots of false hits. Maybe I'll add a local
dictionary and a "spell-check" rule...
next prev parent reply other threads:[~2001-09-27 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 11:56 DJ Delorie
2001-09-27 3:18 ` Eli Zaretskii
2001-09-27 9:57 ` DJ Delorie
2001-09-27 11:49 ` Eli Zaretskii
2001-09-27 12:58 ` DJ Delorie
2001-09-27 12:07 ` Eli Zaretskii
2001-09-27 12:01 ` Phil Edwards
2001-09-27 13:12 ` DJ Delorie [this message]
2001-09-27 13:15 ` Phil Edwards
2001-09-27 13:54 ` Eli Zaretskii
2001-09-27 3:20 ` Eli Zaretskii
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=200109272012.f8RKCCH14283@envy.delorie.com \
--to=dj@delorie.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=pedwards@disaster.jaj.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.
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).