From: Richard Copley <rcopley@gmail.com>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: Emacs Development <emacs-devel@gnu.org>
Subject: Re: M-x send-emacs-patch
Date: Thu, 5 May 2016 22:16:41 +0100 [thread overview]
Message-ID: <CAPM58og3GqHkK85hEb-K8W5CTSim9yQAEgjyz18neTcB3=_FCA@mail.gmail.com> (raw)
In-Reply-To: <572BB50C.5050406@gmail.com>
On 5 May 2016 at 22:03, Clément Pit--Claudel <clement.pit@gmail.com> wrote:
> On 2016-05-05 16:42, Richard Copley wrote:
>> Yes there is, but I wouldn't like to go into it in a public forum.
>> Can patches to a GPL'd project be public domain?
>
> Yes, at least according to http://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright/conditions.text:
>
> This means that if you want to contribute software to GNU, you have to
> do something to give us legal permission to use it. There are three
> ways this can be done:
>
> (...)
>
> * Put the code in the public domain. Then there is nothing to stop
> hoarding of modified versions, but we can still use the program in GNU.
>
> Hopefully that works for you!
Thanks Clément. It's not my place to decide on this, but it doesn't
sound to me as though it addresses my question, which is different
from the question of whether a patch would be acceptable to the FSF;
namely, does the GPL prevent me from putting a modification to a
GPL-licensed work into the public domain in the first place?
next prev parent reply other threads:[~2016-05-05 21:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 23:44 M-x send-emacs-patch Lars Ingebrigtsen
2016-05-04 0:19 ` John Wiegley
2016-05-04 0:38 ` Dmitry Gutov
2016-05-04 0:42 ` Lars Ingebrigtsen
2016-05-04 1:45 ` John Wiegley
2016-05-05 9:06 ` Uwe Brauer
2016-05-05 10:30 ` Yuri Khan
2016-05-05 11:39 ` Kaushal Modi
2016-05-05 12:42 ` Lars Ingebrigtsen
2016-05-05 15:58 ` Kaushal Modi
2016-05-05 20:22 ` Richard Copley
2016-05-05 20:35 ` Clément Pit--Claudel
2016-05-05 20:42 ` Richard Copley
2016-05-05 21:03 ` Clément Pit--Claudel
2016-05-05 21:16 ` Richard Copley [this message]
2016-05-05 21:20 ` Dmitry Gutov
2016-05-05 21:30 ` Richard Copley
2016-05-05 21:37 ` Clément Pit--Claudel
2016-05-05 21:41 ` Richard Copley
2016-05-05 21:48 ` Clément Pit--Claudel
2016-05-05 22:01 ` Richard Copley
2016-05-05 22:27 ` Clément Pit--Claudel
2016-05-06 19:18 ` Richard Stallman
2016-05-06 20:09 ` Clément Pit--Claudel
2016-05-06 20:34 ` Richard Copley
2016-05-07 18:36 ` Richard Stallman
2016-05-05 21:30 ` Clément Pit--Claudel
2016-05-05 21:35 ` Richard Copley
2016-05-06 19:16 ` Richard Stallman
2016-05-06 3:24 ` Lars Ingebrigtsen
2016-05-06 3:50 ` Lars Ingebrigtsen
2016-05-05 9:05 ` Uwe Brauer
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='CAPM58og3GqHkK85hEb-K8W5CTSim9yQAEgjyz18neTcB3=_FCA@mail.gmail.com' \
--to=rcopley@gmail.com \
--cc=clement.pit@gmail.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).