From: Richard Stallman <rms@gnu.org>
Cc: Lute.Kamstra.lists@xs4all.nl, emacs-devel@gnu.org
Subject: Re: authors excludes the lisp manual.
Date: Fri, 13 May 2005 12:08:27 -0400 [thread overview]
Message-ID: <E1DWciB-0000Eb-CO@fencepost.gnu.org> (raw)
In-Reply-To: <851x8cfmpp.fsf@lola.goethe.zz> (message from David Kastrup on Thu, 12 May 2005 18:11:46 +0200)
Could it have anything to do with the fact that the Lisp manual is not
distributed under the GPL?
The specific license of any particular file should not matter for this.
prev parent reply other threads:[~2005-05-13 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 0:34 authors excludes the lisp manual Lute Kamstra
2005-05-12 14:54 ` Richard Stallman
2005-05-12 15:32 ` Lute Kamstra
2005-05-12 16:11 ` David Kastrup
2005-05-13 16:08 ` Richard Stallman [this message]
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=E1DWciB-0000Eb-CO@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=Lute.Kamstra.lists@xs4all.nl \
--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).