From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 78170 invoked by alias); 9 Feb 2016 05:59:31 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 78156 invoked by uid 89); 9 Feb 2016 05:59:30 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:410, teach, H*r:sk:oversee, him X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 09 Feb 2016 05:59:29 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (Postfix) with ESMTPS id D523DC09FA92 for ; Tue, 9 Feb 2016 05:59:28 +0000 (UTC) Received: from [10.3.113.7] ([10.3.113.7]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u195xKoO004323; Tue, 9 Feb 2016 00:59:24 -0500 Subject: Re: Requesting glibc ACLs To: DJ Delorie , overseers@sourceware.org References: <201602090436.u194awK6021160@greed.delorie.com> Cc: codonell@redhat.com From: "Carlos O'Donell" Message-ID: <56B98033.7090703@redhat.com> Date: Tue, 09 Feb 2016 05:59:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <201602090436.u194awK6021160@greed.delorie.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2016-q1/txt/msg00062.txt.bz2 On 02/08/2016 11:36 PM, DJ Delorie wrote: > Please add me to the glibc ACLs after confirming with Carlos. > > I certify that I am sane (mostly), that I understand the rules, and > that I have the appropriate copyright paperwork in place. I support DJ's work on glibc and will teach him to follow the per-branch commit rules, and to understand FSF copyright policy. Cheers, Carlos.