From: Richard Stallman <rms@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: belanger@truman.edu, emacs-devel@gnu.org
Subject: Re: Manual licenses
Date: Mon, 16 Apr 2007 11:37:41 -0400 [thread overview]
Message-ID: <E1HdTGv-0000vL-LT@fencepost.gnu.org> (raw)
In-Reply-To: <87lkgtcow6.fsf@stupidchicken.com> (message from Chong Yidong on Sun, 15 Apr 2007 17:24:09 -0400)
> A couple of manuals (dired-x, the faq) aren't under the GFDL.
I went ahead and relicensed dired-x. Do we can to relicense the FAQ?
It seem to have a special-purpose license, and to be deliberately not
under the GFDL.
The FAQ does have its other license deliberately. I am not sure why.
But we may as well leave it alone.
prev parent reply other threads:[~2007-04-16 15:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 4:41 Manual licenses Jay Belanger
2007-04-15 19:01 ` Richard Stallman
2007-04-15 21:24 ` Chong Yidong
2007-04-16 15:37 ` 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=E1HdTGv-0000vL-LT@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=belanger@truman.edu \
--cc=cyd@stupidchicken.com \
--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).