From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Where is @node Copying in the lispref?
Date: Mon, 05 May 2003 10:32:35 -0400 [thread overview]
Message-ID: <E19Ch19-0000mi-00@fencepost.gnu.org> (raw)
In-Reply-To: <87u1cbqeem.fsf@tleepslib.sk.tsukuba.ac.jp> (stephen@xemacs.org)
But it's not the GPL, is it? The GPL is the license for Emacs itself,
but the lispref is now under the FDL according to the header material.
Would you please lay out the facts of the problem, and why you think
it is a problem. Your description was fragmentary, and I can't tell
if there is a real problem or not. I am unable to follow the subsequent
discussion.
next prev parent reply other threads:[~2003-05-05 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-03 16:33 Where is @node Copying in the lispref? Stephen J. Turnbull
2003-05-03 19:01 ` Eli Zaretskii
2003-05-04 8:55 ` Stephen J. Turnbull
2003-05-05 14:32 ` Richard Stallman [this message]
2003-05-06 10:55 ` Stephen J. Turnbull
2003-05-07 11:51 ` Richard Stallman
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=E19Ch19-0000mi-00@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).