From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Which files to proofread
Date: Sun, 18 Aug 2002 18:50:06 -0600 (MDT) [thread overview]
Message-ID: <200208190050.g7J0o6M09221@wijiji.santafe.edu> (raw)
In-Reply-To: <ap3ofc0amse.fsf@z.glue.umd.edu> (deego@glue.umd.edu)
Thanks for keeping track of what files have been read.
To get good coverage, I think we need each file to be read at least
twice. One person reading a chapter can easily overlook a problem,
because noticing them is hard.
prev parent reply other threads:[~2002-08-19 0:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-12 17:05 Which files to proofread Richard Stallman
2002-08-13 6:36 ` Harald.Maier.BW
2002-09-02 0:02 ` Richard Stallman
2002-09-02 5:14 ` Eli Zaretskii
2002-09-02 0:02 ` Richard Stallman
2002-09-07 10:58 ` Harald.Maier.BW
2002-08-18 3:06 ` D. Goel
2002-08-19 0:50 ` Richard Stallman [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=200208190050.g7J0o6M09221@wijiji.santafe.edu \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.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).