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 587E81F453 for ; Wed, 23 Jan 2019 14:07:38 +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=RtM/4+gGpwiJAF0I yp055bRgAZsMMB+lknUk+vG/6H4Ecx0yxN0Pd+clr8nneEBk4BexXM1Z7A3yGOdg ZU0MhLz0P40B/7wiJTft+xJSwsQm89wf49y+3PODetBImBgCubA8bjgXf1qlMj8s PQQETnPK8UlW8Nrvtk9jdWyyv44= 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=t5zkaLR9NgD71PlTf2LobT 9Cpt0=; b=R1McbdcOkMAM8rgtDNfbB9QnYhETyuoRUC7sG02Odpvy9Xeo+ltm9j yq06ZpF87cAFSi8qEEPKBnFZ9nAW7D86ggNCjg7SUHAFdPzVMMXniugUuT4S0/gq ldIZzGYZ607dwrjpYFkCs3AWpaiBjIQMR26oTQU+2fuy/LUU3A5CI= Received: (qmail 73230 invoked by alias); 23 Jan 2019 14:07:35 -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 73208 invoked by uid 89); 23 Jan 2019 14:07:34 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: mail-qt1-f194.google.com Subject: Re: glibc 2.29 - Winter is coming... To: Feng Xue , Ramana Radhakrishnan Cc: Szabolcs Nagy , Siddhesh Poyarekar , GLIBC Devel , nd 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> <32c3da11-2a60-b168-508e-27cfce4e014a@redhat.com> From: Carlos O'Donell Openpgp: preference=signencrypt Message-ID: <5d49c703-3dde-1175-6230-aed030101c4e@redhat.com> Date: Wed, 23 Jan 2019 09:07:28 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit On 1/23/19 8:40 AM, Feng Xue wrote: > Now it is still in the stage of code freeze for 2.29 release, is it? > And once window is opened that I can me to push those patches myself, > should I need another code-review process on Patchwork? Yes, master is frozen for the 2.29 release. The release is February 1st. If the machine maintainers, particularly Szabolcs or Ramana have reviewed the work and there appears to be consensus that it's correct, then you just need to wait for the branch to open, Siddhesh will announce this, before you push your changes. Please use the ChangeLog as you wrote it with the date adjusted to the day you commit, use a detailed commit message (that was reviewed as part of the submission), and remain attentive in the even that your change breaks something and subsequent rework is needed. Thank you! -- Cheers, Carlos.