From: "Richard M. Stallman" <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Updating manuals
Date: Sun, 19 Oct 2008 21:13:44 -0400 [thread overview]
Message-ID: <E1KrjL6-0001im-P2@fencepost.gnu.org> (raw)
In-Reply-To: <ud4hxll11.fsf@gnu.org> (message from Eli Zaretskii on Sat, 18 Oct 2008 22:12:58 +0200)
I think it is better to insist that people provide full
descriptions for NEWS, rather than that they write text for
the manual. If we install text in the manual from someone
who isn't good at technical writing, it will be very likely that people
fail to rewrite it, and it will be released with bad writing and/or
errors in Texinfo usage.
next prev parent reply other threads:[~2008-10-20 1:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 20:12 Updating manuals Eli Zaretskii
2008-10-19 2:45 ` Chong Yidong
2008-10-19 7:28 ` Eli Zaretskii
2008-10-19 14:55 ` Chong Yidong
2008-10-20 1:13 ` Richard M. Stallman [this message]
2008-10-20 8:33 ` 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
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=E1KrjL6-0001im-P2@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@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).