From: Richard Stallman <rms@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 12973@debbugs.gnu.org
Subject: bug#12973: [TRUNCATED MESSAGE 2692 191817] bug#12973: @: overused in manual
Date: Sat, 24 Nov 2012 23:47:09 -0500 [thread overview]
Message-ID: <E1TcU7Z-0006bS-CY@fencepost.gnu.org> (raw)
In-Reply-To: <50B16A6A.9000701@cs.ucla.edu> (message from Paul Eggert on Sat, 24 Nov 2012 16:46:34 -0800)
> We should correct these style issues for each Emacs release.
Our release strategy makes it difficult to fix these style
changes now: if we made changes like these, either to
the trunk or to the emacs-24 branch, that'd make it harder
to merge other emacs-24 changes into the trunk later.
I don't think we are talking about the same thing.
You seem to be criticizing a specific plan for installing the changes
into the Bzr repository. I'm not talking about mechanics like that.
I'm saying that someone should edit the manual for style and usage for
each release. Precisely when in the release style is a detail that I
leave to others, but I would normally do it before making a separate
branch for a given release. If it is done after that, the changes
should be installed in both the trunk and the branch.
While we're on the topic, the Emacs manual has similar problems with
"@.". Sometimes it uses "@." when it's not necessary,
An unnecessary use of @. is not an error.
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
Use Ekiga or an ordinary phone call
next prev parent reply other threads:[~2012-11-25 4:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 19:25 bug#12973: @: overused in manual Paul Eggert
2012-11-23 19:46 ` Eli Zaretskii
2012-11-23 20:50 ` Paul Eggert
2012-11-23 21:47 ` Eli Zaretskii
2012-11-23 23:51 ` Stephen Berman
2012-11-23 23:56 ` Paul Eggert
2012-11-24 0:11 ` Stephen Berman
2012-11-24 6:32 ` Eli Zaretskii
2012-11-24 18:37 ` Richard Stallman
2012-11-24 20:39 ` Eli Zaretskii
2012-11-24 1:43 ` Richard Stallman
2012-11-24 20:31 ` Paul Eggert
2012-11-24 2:03 ` Glenn Morris
2012-11-24 6:33 ` Eli Zaretskii
2012-11-24 6:45 ` Paul Eggert
2012-11-24 7:44 ` Eli Zaretskii
2012-11-24 15:17 ` Stefan Monnier
2012-11-24 15:45 ` Eli Zaretskii
2012-11-24 20:35 ` Stefan Monnier
2012-11-24 18:37 ` Richard Stallman
2012-11-25 0:46 ` Paul Eggert
2012-11-25 4:47 ` Richard Stallman [this message]
2012-11-25 19:17 ` Glenn Morris
2012-11-25 19:16 ` Glenn Morris
2012-11-26 1:31 ` Glenn Morris
2012-12-05 22:31 ` Paul Eggert
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=E1TcU7Z-0006bS-CY@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=12973@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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).