unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Daniel Pittman <slippycheeze@google.com>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: Licensing for source code contained in Emacs manuals
Date: Tue, 13 Nov 2018 13:31:30 -0500	[thread overview]
Message-ID: <jqin1025j1.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAC45yQu0Cvk2qXyEEB0uuL8iJO3ma4ZzGz40Szm0LM_=qFSSrg@mail.gmail.com> (Daniel Pittman's message of "Mon, 12 Nov 2018 16:35:58 -0500")


(Dropped licensing@fsf. I would think just mailing rms would be more
direct/efficient in this instance.)

Daniel Pittman wrote:

> My plan, then, is to give the FSF licensing folks a chance to speak up, and
> then submit a patch that will adjust the licensing text used for the
> various manuals appropriately.

Maybe this is what you mean, but I would think you need explicit
permission from the FSF for this kind of change rather than assuming
silence is consent.



  reply	other threads:[~2018-11-13 18:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-12 18:24 Licensing for source code contained in Emacs manuals Daniel Pittman
2018-11-12 20:01 ` Paul Eggert
2018-11-12 21:35   ` Daniel Pittman
2018-11-13 18:31     ` Glenn Morris [this message]
2018-11-14 23:13       ` Richard Stallman
2018-11-19 14:18         ` Daniel Pittman
2018-11-20  0:49           ` Richard Stallman
2018-12-24  2:26 ` Richard Stallman
2019-01-07 21:06   ` Daniel Pittman
2019-01-08  1:06     ` Paul Eggert
2019-01-08 18:57     ` Richard Stallman
2019-06-30  5:05     ` FIXME: When the reader is called in the minibuffer Spenser Truex
2019-06-30 13:50       ` Stefan Monnier

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=jqin1025j1.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=slippycheeze@google.com \
    /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).