This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 0/5] Using LLVM (DragonEgg) to compile glibc
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Peter Collingbourne <pcc at google dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Tue, 14 May 2013 17:14:20 -0400
- Subject: Re: [PATCH 0/5] Using LLVM (DragonEgg) to compile glibc
- References: <1368459372-2415-1-git-send-email-pcc at google dot com> <51914BC0 dot 6090703 at redhat dot com> <CAMn1gO44Z=wwiQ3jdgOGim0_eG8=t71Wg78+zuCBJ8M6BL_cSg at mail dot gmail dot com>
On 05/14/2013 12:49 PM, Peter Collingbourne wrote:
> On Mon, May 13, 2013 at 10:23 PM, Carlos O'Donell <carlos@redhat.com> wrote:
>> Peter,
>>
>> We are a consensus driven community, so if you get enough ACK's
>> for your patches and work through the objections presented then
>> you should feel free to ask someone to check it in for you.
>
> Thanks Carlos. Do I have enough consensus to ask for patches 2-5 to
> be checked in?
I'd say 2, 3, and 4 could be checked in by a maintainer.
I'm knee deep in Intel TSX patch review right now.
If you can find someone else to help you that would be good.
Make friends with someone on the list:
http://sourceware.org/glibc/wiki/MAINTAINERS#Maintainers_for_libc_and_ports_add-on
Just a friendly reminder:
http://sourceware.org/glibc/wiki/Contribution%20checklist
And remind the committer:
http://sourceware.org/glibc/wiki/Committer%20checklist
>> Alternatively you could express an interest in helping to continue
>> to maintain glibc's ability to be compiled by LLVM and ask for
>> a sourceware account and permission to checkin the glibc changes
>> yourself :-)
>
> Hmm, we'll see.
Just throwing it out there.
Cheers,
Carlos.