unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: emacs-devel@gnu.org
Subject: Re: Where is @node Copying in the lispref?
Date: Tue, 06 May 2003 19:55:35 +0900	[thread overview]
Message-ID: <87brygpcns.fsf@tleepslib.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <E19Ch19-0000mi-00@fencepost.gnu.org> (Richard Stallman's message of "Mon, 05 May 2003 10:32:35 -0400")

>>>>> "rms" == Richard Stallman <rms@gnu.org> writes:

    rms> Would you please lay out the facts of the problem, and why
    rms> you think it is a problem.  Your description was fragmentary,
    rms> and I can't tell if there is a real problem or not.  I am
    rms> unable to follow the subsequent discussion.

The file elisp.texi declares

------------------------------------------------------------------------
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.1 or
any later version published by the Free Software Foundation; with the
Invariant Sections being ``Copying'', with the Front-Cover texts being
``A GNU Manual'', and with the Back-Cover Texts as in (a) below.  A copy
of the license is included in the section entitled ``GNU Free
Documentation License''.
------------------------------------------------------------------------

The section "Copying" is referenced here as an invariant section, and
in several menus in vol1.texi and vol2.texi (perhaps they are
obsolete?), but does not exist in the Lispref in CVS head as far as I
could find (ie, 'fgrep Copying *.texi*').  I believe that this makes
all copying of the Lispref risky, even verbatim copying, as it appears
that the legally required section may be missing.  I suspect it makes
modified versions illegal.

My guess was that the invariant section needs to refer to the node
containing the FDL.  Either the node could be renamed to "Copying" or
the invariant section could be changed to "GNU Free Documentation
License".

Eli said that it's the GNU GPL that is the intended invariant section,
in which case the invariant section would be "GNU General Public
License".

Looking at the example of the Emacs manual (where "Copying" == the GPL,
"Distribution", and "The GNU Manifesto" are invariant), I guess that's
the likely possibility.


N.B. If vol1.texi and vol2.texi are obsolete, they should be removed,
I think.  Else they probably should be updated to correspond to the
menu in elisp.ref.  Furthermore, they appear to contain different
licensing terms for the lispref (namely, the GPL).


-- 
Institute of Policy and Planning Sciences     http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.

  reply	other threads:[~2003-05-06 10:55 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
2003-05-06 10:55       ` Stephen J. Turnbull [this message]
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=87brygpcns.fsf@tleepslib.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.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).