From: Ian Lance Taylor <iant@google.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Nick Clifton <nickc@redhat.com>, binutils@sourceware.org
Subject: Re: Switching GAS to GPLv3
Date: Tue, 03 Jul 2007 14:51:00 -0000 [thread overview]
Message-ID: <m3fy45ft07.fsf@localhost.localdomain> (raw)
In-Reply-To: <20070703113243.GF4603@sunsite.mff.cuni.cz>
Jakub Jelinek <jakub@redhat.com> writes:
> On Tue, Jul 03, 2007 at 12:00:53PM +0100, Nick Clifton wrote:
> > I have checked in a patch to switch all of the source files in the
> > gas/ directory over to version 3 of the GPL. I will be updating the
> > other binutils directories over the next few days.
>
> What does this mean for backporting fixes from binutils trunk to older
> binutils releases?
> Does this mean backports are not possible at all, or do we have to
> relicense our legacy releases (that we want to backport stuff to) to GPLv3?
As far as I can see, the only issue that would arise would be if the
copyright assignment of the person contributing the patch specified
that the patch could only be used with GPLv3 or above. Since the FSF
owns the copyright of any contributed patch (or the copyright has been
disclaimed), the FSF can release the patch under any license which the
copyright assignment permits. And the standard copyright assignment
certainly permits GPLv2.
Ian
next prev parent reply other threads:[~2007-07-03 14:43 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 [this message]
2007-07-11 16:19 ` Nick Clifton
2007-07-23 15:51 ` Ralf Corsepius
2007-07-23 20:29 ` Bernd Jendrissek
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=m3fy45ft07.fsf@localhost.localdomain \
--to=iant@google.com \
--cc=binutils@sourceware.org \
--cc=jakub@redhat.com \
--cc=nickc@redhat.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.
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).