This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.18: One month left!
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Steve Langasek <steve dot langasek at canonical dot com>
- Cc: Aurelien Jarno <aurelien at aurel32 dot net>, David Miller <davem at davemloft dot net>, aj at suse dot com, libc-alpha at sourceware dot org
- Date: Tue, 14 May 2013 01:53:10 -0400
- Subject: Re: glibc 2.18: One month left!
- References: <517968C4 dot 9030503 at redhat dot com> <518BBEF9 dot 8050006 at suse dot com> <20130509 dot 140921 dot 276881894943786508 dot davem at davemloft dot net> <518C1869 dot 7070402 at redhat dot com> <20130509220143 dot GI31148 at hall dot aurel32 dot net> <20130514054424 dot GA23300 at virgil dot dodds dot net>
On 05/14/2013 01:44 AM, Steve Langasek wrote:
> Hi Aurelien,
>
> On Fri, May 10, 2013 at 12:01:43AM +0200, Aurelien Jarno wrote:
>> On Thu, May 09, 2013 at 05:43:05PM -0400, Carlos O'Donell wrote:
>>> On 05/09/2013 05:09 PM, David Miller wrote:
>>>> From: Andreas Jaeger <aj@suse.com>
>>>> Date: Thu, 09 May 2013 17:21:29 +0200
>>>>
>>>>> I also encourage distributions to look for patches that they care and
>>>>> send them in for review,
>>>>
>>>> On this note, I really can't believe we still haven't seen a
>>>> submission of Debian's multiarch stuff.
>>>>
>>>> That critically blocks my ability to test on sparc.
>
>>> How big is the patch?
>
>>> Is copyright status sorted?
>
>>> If copyright status is sorted I'd just check it in.
>
>> I didn't know that glibc was interested by multiarch, that's why the
>> patch haven't been submitted yet.
>
>> There is no real multiarch support patch (at least for the glibc side),
>> most of the work is done by passing the correct configure options. The
>> patches mostly add support for non-common values.
>
>> I have identified 3 patches changing around 50 lines each, that are part
>> of the multiarch support. The authors are Steve Langasek and myself. I
>> don't know if has done the copyright paperwork, I have Cced: him.
>
> Sorry, the email address you used for me (@linaro.org) is no longer valid.
> However, it's still the right email address to use in reference to my
> multiarch patches for glibc, in the sense that those patches were all
> developed while under contract to Linaro. My best understanding is that
> this means they're covered by a blanket copyright assignment agreement under
> Linaro and the FSF, or if not Linaro, then Canonical and the FSF. Cf.
> <https://wiki.linaro.org/Copyright>. However, I don't know the details of
> any standing copyright assignment agreements that would cover glibc;
> hopefully someone on the glibc side is able to check this.
If you did the work while at Linaro then you would be covered
under their blanket copyright assignment by virtue of the contract
you signed to work at Linaro.
Cheers,
Carlos.