From: Jesse W <jessw@netwood.net>
To: karl@freefriends.org (Karl Berry)
Cc: 1988@emacsbugs.donarmstrong.com, rms@gnu.org
Subject: bug#1988: Making the license statement visible in the Emacs Manual
Date: Wed, 28 Jan 2009 16:25:37 -0800 [thread overview]
Message-ID: <d735bd660b617263513ec8c3a444a96f@netwood.net> (raw)
In-Reply-To: <200901282338.n0SNcI905573@f7.net>
On Jan 28, 2009, at 3:38 PM, Karl Berry wrote:
> I can imagine either:
>
> 1) adding @insertcopying to the Top node, which is simple but adds ~20
> lines of text (the full copying notice), or
>
> 2) adding just a sentence saying to look at the source for the precise
> conditions, something like this:
>
> This manual is released under the GNU Free Documentation License.
> For the full copying conditions, please view the full source for
> this formatted file (e.g., @code{g*} in Info, View Source in
> HTML).
>
> Do any of you have a preference for which way to go?
Simply adding @insertcopying seems best to me, but any of the
alternatives are fine. If it would help, I'd be happy to make patches
for the various manuals.
Jesse Weinstein
next prev parent reply other threads:[~2009-01-29 0:25 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 [this message]
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
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=d735bd660b617263513ec8c3a444a96f@netwood.net \
--to=jessw@netwood.net \
--cc=1988@emacsbugs.donarmstrong.com \
--cc=karl@freefriends.org \
--cc=rms@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).