From: karl@freefriends.org (Karl Berry)
To: jessw@netwood.net
Cc: 1988@emacsbugs.donarmstrong.com
Subject: bug#1988: Making the license statement visible in the Emacs Manual
Date: Fri, 6 Feb 2009 17:02:43 -0600 [thread overview]
Message-ID: <200902062302.n16N2hH08980@f7.net> (raw)
In-Reply-To: <dbbcd8bc26f4768af68856d252c48bbc@netwood.net>
On review, I think you're right. I was being overly cautious. Here's
a patch that puts it right in the opening screenfull, where it
certainly won't be missed.
Ok.
Certainly. By "the other manuals" I assume you mean those listed on:
http://www.gnu.org/manual/manual.html --
No. Sorry for not specifying. I just mean the manuals in the Emacs
distribution, namely those here:
http://cvs.savannah.gnu.org/viewvc/emacs/doc/?root=emacs
(There are many individual manuals in the misc/ subdir.)
Dealing with manuals in other distributions has to be done separately,
through their respective maintainers/bug lists. If you want to take
that on, that would be great.
BTW, (I know this should likely be mentioned elsewhere, but...) GNUMP3d
should probably be noted as being "mothballed" per it's developer's
comment here: http://www.gnu.org/software/gnump3d/index.html
Hmm, thanks for mentioning it. I guess I'll be writing to its maintainer.
next prev parent reply other threads:[~2009-02-06 23:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 8:16 bug#1988: Making the license statement visible in the Emacs Manual Jesse W
2009-01-26 7:38 ` Glenn Morris
2009-01-26 18:33 ` Jesse W
2009-01-26 18:41 ` Glenn Morris
2009-01-26 21:28 ` Jesse W
2009-01-26 22:45 ` Eli Zaretskii
2009-01-27 22:59 ` Richard M Stallman
2009-01-28 4:04 ` Eli Zaretskii
2009-01-28 23:38 ` Karl Berry
2009-01-29 0:25 ` Jesse W
2009-02-01 14:37 ` Karl Berry
2009-02-05 9:29 ` Jesse W
2009-02-06 0:05 ` Karl Berry
2009-02-06 19:03 ` Jesse W
2009-02-06 23:02 ` Karl Berry [this message]
2009-02-08 19:38 ` Jesse W
2009-02-16 17:50 ` Karl Berry
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=200902062302.n16N2hH08980@f7.net \
--to=karl@freefriends.org \
--cc=1988@emacsbugs.donarmstrong.com \
--cc=jessw@netwood.net \
/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).