unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: "Richard Copley" <rcopley@gmail.com>,
	"Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: Emacs Development <emacs-devel@gnu.org>
Subject: Re: M-x send-emacs-patch
Date: Fri, 6 May 2016 00:20:44 +0300	[thread overview]
Message-ID: <c557ac61-c7ad-fb1d-7eb6-36065cfa1848@yandex.ru> (raw)
In-Reply-To: <CAPM58og3GqHkK85hEb-K8W5CTSim9yQAEgjyz18neTcB3=_FCA@mail.gmail.com>

On 05/06/2016 12:16 AM, Richard Copley wrote:

> 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?

Your code will be public domain. The combined work will still be GPL.

Actually releasing your changes in the public domain in the way accepted 
by FSF will require paperwork anyway, so you must have a very particular 
reason to choose this route.



  reply	other threads:[~2016-05-05 21:20 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
2016-05-05 21:20                       ` Dmitry Gutov [this message]
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=c557ac61-c7ad-fb1d-7eb6-36065cfa1848@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=clement.pit@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rcopley@gmail.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).