[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [patches] Fw: What license is acceptable for libdecnumber
- To: rsa@xxxxxxxxxx
- Subject: Re: [patches] Fw: What license is acceptable for libdecnumber
- From: Jim Blandy <jimb@xxxxxxxxxxxxxxxx>
- Date: Tue, 25 Sep 2007 09:46:59 -0700
"Ryan S. Arnold" <rsa@xxxxxxxxxx> writes:
> On Thu, 2007-09-20 at 12:48 -0700, Jim Blandy wrote:
>> "Ryan S. Arnold" <rsa@xxxxxxxxxx> writes:
>> > The license is currently LGPLv2. The code on penguinppc.org is
>> > necessarily IBM copyright (because we aren't giving it up if no-one
>> > wants it) though we all have FSF copyright assignment and we intend to
>> > assign copyright to FSF once it's accepted into EGLIBC.
>>
>> Hi, Ryan. The EGLIBC repository policy permits code not assigned to
>> the FSF on branches, but only FSF-assigned code on the trunk. So I
>> think IBM should go ahead and commit libdfp to a branch in the EGLIBC
>> repository, under some appropriate name under
>> svn+ssh://eglibc/org/branches. (If you have any Subversion usage
>> questions, let me know.) Then we can review and revise from there,
>> get things approved, get things assigned, and then merge to trunk.
>
> Thanks Jim,
>
> Peter, Any ETA on when we could get libdfp into it's own branch?
>
> Jim I assume we can do the basefile override -> conditional code changes
> in the branch as well or would you like to see a first draft checked
> into the branch first?
I think whatever works better for you folks will be fine. We just
want to be able to review what will actually be going in.