From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 767A21F803 for ; Wed, 9 Jan 2019 16:05:54 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:cc:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=p4jm8/w7EsykBZTR 92HJOIWsz0GJz3USzFhAIDMdAtAKYLlFT3WVuT0VCU+7w25LFzg/qvDdbSPZ6b2S hXKv3y4AzFqFon4/qD+odTRcAqTGwbQAta+3pMwPcWSonEAuP6px3HIN1fmWFpLm yCQopLAtSv3HxIkhLP9S/C+LrHg= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:cc:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=kRdk+DvcwWH5wArYjtpyN0 i5kRE=; b=nowARPbr5NEm03FhjX+xGpRWm4F/up+keYUAyw4DH4V7flTh/VJU/q 0cpYc+5c+U/bOHGd9ju3Mj+m05YXr9tOo9/gnigvqzRQ12Zq81SoE3ZsZGPx2tKE IJShvVsw90qmgDlRNqRpLCzpIw0oXEAdVGkUERXelh70AoCi/j5ek= Received: (qmail 56891 invoked by alias); 9 Jan 2019 16:05:51 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 56879 invoked by uid 89); 9 Jan 2019 16:05:51 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: mail-qt1-f179.google.com Subject: Re: glibc 2.29 - Winter is coming... To: Ramana Radhakrishnan Cc: Szabolcs Nagy , Siddhesh Poyarekar , GLIBC Devel , nd , Feng Xue References: <833db514-f25e-0c41-bf06-b8cc9272f1c2@gotplt.org> <37cd6bec-71c2-16f8-48dd-f362b5a71cea@arm.com> <056134a0-469a-749f-caae-62299845a31b@redhat.com> <8bbf8ed3-e593-b232-28f7-919f9534a798@redhat.com> From: Carlos O'Donell Openpgp: preference=signencrypt Message-ID: <32c3da11-2a60-b168-508e-27cfce4e014a@redhat.com> Date: Wed, 9 Jan 2019 11:03:32 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit On 1/9/19 5:50 AM, Ramana Radhakrishnan wrote: > On Tue, Jan 8, 2019 at 4:50 PM Carlos O'Donell wrote: >> >> On 1/8/19 9:21 AM, Szabolcs Nagy wrote: >>> On 08/01/2019 14:16, Carlos O'Donell wrote: >>>> On 1/8/19 8:33 AM, Szabolcs Nagy wrote: >>>>> On 02/01/2019 10:28, Siddhesh Poyarekar wrote: >>>>>> Status of Release blockers: >>>>>> >>>>>> I have reviewed all original release blockers, including a couple of additional ones that got added later but I couldn't get to all of them. As >>>>>> of now, the pending blockers do not look suitable for inclusion at this stage and so will be deferred to 2.30 development. >>>>> >>>>> i'd like to commit some patches that only affect aarch64 >>>>> (and only particular uarches there): >>>>> >>>>> memchr and memset for AmpereComputing emag (approved before freeze): >>>>> https://sourceware.org/ml/libc-alpha/2018-12/msg00626.html >>>>> https://sourceware.org/ml/libc-alpha/2018-12/msg00628.html >>>>> https://sourceware.org/ml/libc-alpha/2018-12/msg00820.html >>>> >>>> AmpereComputing is not yet listed in the FSF copyright files, >>>> and I don't have confirmation from the FSF (it has been asked). >>> >>> ah, my bad then. >> >> Sorry, my intent was only to specify that there is a blocker on >> these patches. I am working with Feng Xue directly such that once >> the copyright status is confirmed, I can move forward with account >> setup so AmpereComputing can commit their own approved patches. > > I saw the copyright assignment go past on the GCC side when it > happened and see this in copyright.list on fencepost .. > > GCC GLIBC Ampere Computing LLC 2018-12-05 > Assigns Past and Future Changes > Mauri Whalen (Vice President Software Engineering) Correct, I saw this too and I'm working on the account setup. -- Cheers, Carlos.