From: "Bernd Jendrissek" <bernd.jendrissek@gmail.com>
To: "Ralf Corsepius" <ralf.corsepius@rtems.org>
Cc: binutils@sourceware.org
Subject: Re: Switching GAS to GPLv3
Date: Mon, 23 Jul 2007 20:29:00 -0000 [thread overview]
Message-ID: <b39469680707230851n2a68a71k2865edaafc5e6378@mail.gmail.com> (raw)
In-Reply-To: <1185202505.10535.66.camel@mccallum.corsepiu.local>
Ralf Corsepius wrote:
> In my understanding everybody who submits patches to binutils must have
> a copyright assignment to the FSF on file (unless patches are considered
> trivial).
>
> I am I wrong in presuming that a patch contributed under a copyright
> assignment can be implied to cover GPLv2 and GPLv3?
>
> In other words, if I's submit a patch against a GPLv3'd version of a
> package I'd implicitly assume my patch also to be applicable to a
> GPLv2'd version of the package.
My assignment (which I have not yet returned - bad me!) includes:
"d) FSF agrees to grant back to Developer, and does hereby grant,
non-exclusive, royalty-free and non-cancellable rights to use the
Works (i.e., Developer's changes and/or enhancements, not the Program
that they enhance), as Developer sees fit; this grant back does not
limit FSF's rights and public rights acquired through this agreement."
The answer to your question, AFAICT, hinges on whether your patch is a
derived work or not (surely it is, otherwise an Evil Empire can do
diff -N -u10000 /src/binutils /emptydir >/tmp/proprietary.diff???) and
if so, what the licence of the derived-from work is.
But if you download a GPLv2 tarball before August and run diff between
it and your subsequent modified copy, then I reckon you can do
whatever you want with that patch, as long as you obey the GPLv2 (due
to the tarball's pre-August licence). You just can't sue anyone for
what they do with your patch, because only the FSF has the right to do
so.
Then again, IANAL.
next prev parent reply other threads:[~2007-07-23 15:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 11:30 Nick Clifton
2007-07-03 12:43 ` Jakub Jelinek
2007-07-03 14:27 ` Nick Clifton
2007-07-03 14:51 ` Ian Lance Taylor
2007-07-11 16:19 ` Nick Clifton
2007-07-23 15:51 ` Ralf Corsepius
2007-07-23 20:29 ` Bernd Jendrissek [this message]
2007-07-24 11:01 ` Nick Clifton
2007-07-03 13:30 ` l l
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=b39469680707230851n2a68a71k2865edaafc5e6378@mail.gmail.com \
--to=bernd.jendrissek@gmail.com \
--cc=binutils@sourceware.org \
--cc=ralf.corsepius@rtems.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.
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).