From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: checking manual files
Date: Tue, 09 Aug 2005 17:46:36 -0400 [thread overview]
Message-ID: <E1E2bvg-0003nv-C0@fencepost.gnu.org> (raw)
In-Reply-To: <m38xzbl31j.fsf@naru.home> (message from Joakim Verona on Tue, 09 Aug 2005 14:15:20 +0200)
I've checked some manual files in in the past, and can do a couple
more now, to help with the release.
Which ones are in a state worth checking now?
All of them are in a state worth checking.
But there is a list in admin/FOR-RELEASE
of who has checked what. I would like each file to be
checked twice--in that file you can see which ones have
not been checked twice.
prev parent reply other threads:[~2005-08-09 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 12:15 checking manual files Joakim Verona
2005-08-09 21:46 ` Richard M. 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=E1E2bvg-0003nv-C0@fencepost.gnu.org \
--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).