From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: emacs.texi
Date: Thu, 05 Oct 2006 00:15:01 -0400 [thread overview]
Message-ID: <E1GVKdR-00005m-6R@fencepost.gnu.org> (raw)
In-Reply-To: <m3u02kz52y.fsf@kfs-l.imdomain.dk> (storm@cua.dk)
The program is fine for updating AUTHORS, but the two lists
of people in the manual are meant for human readers and they
need to be written properly by hand.
Is there a criteria for (in|ex)clusion in the list in emacs.texi?
We include people who have contributed new files or major changes.
next prev parent reply other threads:[~2006-10-05 4:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 23:40 emacs.texi Richard Stallman
2006-10-04 7:47 ` emacs.texi David Kastrup
2006-10-04 11:35 ` emacs.texi Kim F. Storm
2006-10-05 4:15 ` Richard Stallman [this message]
2006-10-05 4:15 ` emacs.texi Richard Stallman
2006-10-04 14:21 ` emacs.texi Chong Yidong
2006-10-05 4:15 ` emacs.texi Richard Stallman
2006-10-05 11:19 ` emacs.texi Kim F. Storm
2006-10-05 20:29 ` emacs.texi Richard Stallman
2006-10-06 22:25 ` emacs.texi Kim F. Storm
2006-10-07 20:11 ` emacs.texi Richard Stallman
2006-10-07 20:32 ` emacs.texi David Kastrup
2006-10-08 16:16 ` emacs.texi Richard Stallman
2006-10-07 23:06 ` emacs.texi Kim F. Storm
2006-10-09 9:43 ` emacs.texi Johan Bockgård
2006-10-09 11:11 ` emacs.texi Kim F. Storm
2006-10-09 19:52 ` emacs.texi Eli Zaretskii
2006-10-09 20:35 ` emacs.texi Karl Berry
2006-10-10 4:14 ` emacs.texi Eli Zaretskii
2006-10-10 8:14 ` emacs.texi David Kastrup
2006-10-10 21:16 ` emacs.texi Eli Zaretskii
2006-10-10 8:46 ` emacs.texi Kim F. Storm
2006-10-10 21:17 ` emacs.texi Eli Zaretskii
2006-10-10 22:40 ` emacs.texi Kim F. Storm
2006-10-10 23:44 ` emacs.texi Karl Berry
-- strict thread matches above, loose matches on Subject: below --
2006-10-06 22:38 emacs.texi Nick Roberts
2006-10-06 23:34 ` emacs.texi Kim F. Storm
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=E1GVKdR-00005m-6R@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).