all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: feedmail.el in the public domain?
Date: Sat, 15 Sep 2018 15:13:50 -0700	[thread overview]
Message-ID: <d0afbaff-c5d2-d60c-1e9f-880e71bff8be@cs.ucla.edu> (raw)
In-Reply-To: <83h8isj59j.fsf@gnu.org>

Eli Zaretskii wrote:
> We've been through this, you should be able to find the relevant
> discussions in the archives.  This file is in public domain and cannot
> be changed to anything else, AFAIR.

I couldn't find the relevant discussions despite three or four Google searches; 
could you briefly elaborate?

If a file is in the public domain then there is no legal obstacle to placing 
whatever copyright license you like on a copy that you redistribute. At least 
that's true in the US, which is the controlling legal authority for FSF 
distribution. If there's some foreign-copyright issue here, we may need to have 
FSF legal counsel look at it, since these things can be tricky.



  reply	other threads:[~2018-09-15 22:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-14 14:44 feedmail.el in the public domain? Stefan Monnier
2018-09-14 18:36 ` Eli Zaretskii
2018-09-15 22:13   ` Paul Eggert [this message]
2018-09-16 17:49     ` Eli Zaretskii
2018-09-16 19:59       ` Paul Eggert
2018-09-17  2:25         ` Richard Stallman
2018-09-17  3:00           ` Stefan Monnier
2018-09-17  4:12             ` Paul Eggert
2018-09-17 14:17               ` Eli Zaretskii
2018-09-17 15:12                 ` Stefan Monnier
2018-09-17 22:53                   ` Richard Stallman
2018-09-18  2:53                     ` Stefan Monnier
2018-09-18  3:12                       ` Glenn Morris
2018-09-17 22:52                 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d0afbaff-c5d2-d60c-1e9f-880e71bff8be@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.