From: Andrew Haley <aph@redhat.com>
To: java@gcc.gnu.org
Subject: Re: Which library implementation to use/work on?
Date: Wed, 14 Mar 2012 11:12:00 -0000 [thread overview]
Message-ID: <4F607D21.1080900@redhat.com> (raw)
In-Reply-To: <CANEZrP2dbhAnF739V=766yuLnn+K9wGF_VT0njmU2G4q=X5CRw@mail.gmail.com>
On 03/14/2012 11:11 AM, Mike Hearn wrote:
>>> I understand the reasons for this policy. However, as you are planning
>>> on (eventually) replacing Classpath with OpenJDK completely, an
>>> exception in this case would seem to make logical sense. The code will
>>> end up not owned by the FSF no matter what.
>>
>> Well, no. The FSF will still own Classpath.
>
> Yes. But drawing a line in the sand and saying "after this point, we
> no longer have the ability to relicense as we wish, but that's OK
> because we don't care about this codebase anymore" seems prudent as a
> migration strategy.
We're not there yet.
> My basic issue is, given license compatibility, reimplementing things
> purely so the FSF has the option of relicenseing a codebase that it
> probably never will is not a good use of time. In practice it just
> means people won't submit patches because unless they're working on
> AWT or some other library where copy/pasting code is hard, it never
> makes sense to upstream patches. That in turn makes it harder for
> people to benefit from those patches.
Fair enough.
Andrew.
next prev parent reply other threads:[~2012-03-14 11:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 16:57 Mike Hearn
2012-03-13 17:07 ` Andrew Haley
2012-03-13 18:26 ` Mike Hearn
2012-03-13 18:39 ` Andrew Haley
2012-03-14 10:40 ` Mike Hearn
2012-03-14 10:43 ` Chris Burdess
2012-03-14 11:11 ` Mike Hearn
2012-03-14 11:12 ` Andrew Haley [this message]
2012-03-14 12:14 ` Andrew Hughes
2012-03-14 12:17 ` Mike Hearn
2012-03-14 12:31 ` Andrew Hughes
2012-03-14 12:35 ` Mike Hearn
2012-03-14 18:32 ` Andrew Hughes
2012-03-15 12:24 ` Mike Hearn
2012-03-15 12:37 ` Andrew Hughes
2012-04-07 15:29 ` Mike Hearn
2012-04-07 18:28 ` Bryce McKinlay
2012-04-08 13:18 ` Mike Hearn
2012-04-10 15:53 ` Mike Hearn
[not found] ` <CANEZrP2ukT8zjNjma9yBREJ6wEuhdU6Qb=bPSOjemTYjzwrH5g@mail.gmail.com>
[not found] ` <CANEZrP0QcpHjxKHWoi=A8+CcE2gPzm2_eO4_PG5=BmMHj-f_+Q@mail.gmail.com>
2012-05-30 21:14 ` Mike Hearn
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=4F607D21.1080900@redhat.com \
--to=aph@redhat.com \
--cc=java@gcc.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.
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).