From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id E637C3857410 for ; Tue, 19 Jul 2022 10:16:03 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org E637C3857410 Received: from mail-qt1-f200.google.com (mail-qt1-f200.google.com [209.85.160.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-42-f6q6uhLlPgSKbPQaLRJX4Q-1; Tue, 19 Jul 2022 06:15:56 -0400 X-MC-Unique: f6q6uhLlPgSKbPQaLRJX4Q-1 Received: by mail-qt1-f200.google.com with SMTP id q21-20020ac84115000000b0031bf60d9b35so9894731qtl.4 for ; Tue, 19 Jul 2022 03:15:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5BhY+8hmlt7HTsCZBrFBaW1XNUgHSoROhtAzj4U9iUc=; b=0L7Xxr2/a9NUIvDCeA6THOkDdnT3OYHKXqzJY5SPnKpLe92+1g+/ntwupRurBjuKlD iGr035b0HjydTY43DiOcm2x6dQtpTot40TpEFdz2oDfyva6Ffc/eoQUnmo/FOpox0fMy +RhqKxJbpPzwQNsA1xzVIV47mAZhnqz8xdaFxC72mA9w+S2TRYastioALuukzzV5wQXw NUJZ41xKeQNOO1IhQcbv4veLL+u6jje0ZzfEATmCom0yINeUvI+DUo81Kw9ExXISBTbt bUXvxAs6Bx6dYuwmfv7ebM+5dqzNLvZNVKSeaFjdUL6GKawF7FEJUqzfdh0rLtCS6RcF XynQ== X-Gm-Message-State: AJIora+Z4C7OiSjWvFAtJqOu5NnWMv4AuVhJ28+UcjycJUgngKBKv9rn QQJPNMq17Qw6j5E494A9iQpVGfTwVaBBdaQRfLH0PDgHTljTJiFB/YP77PhYqf+68FAEN6Z6mQS kQGRBLMreSzrNF5Pi8CaN7UsOnAlpugA= X-Received: by 2002:a05:620a:269a:b0:6b5:b769:2591 with SMTP id c26-20020a05620a269a00b006b5b7692591mr19569614qkp.293.1658225756253; Tue, 19 Jul 2022 03:15:56 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tg9jZM9hLPTbR4AZNZll4r6lWtP/TBmwKljOv1a5cUioRuOTXsGFi5HdWxC36Pjg08xlN1BMfU0nU98nXeW9U= X-Received: by 2002:a05:620a:269a:b0:6b5:b769:2591 with SMTP id c26-20020a05620a269a00b006b5b7692591mr19569604qkp.293.1658225756050; Tue, 19 Jul 2022 03:15:56 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Jonathan Wakely Date: Tue, 19 Jul 2022 11:15:45 +0100 Message-ID: Subject: Re: Re: [PATCH] libstdc++: Make __from_chars_alnum_to_val conversion explicit To: Marco Falke Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-6.7 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: libstdc++@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libstdc++ mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2022 10:16:04 -0000 On Tue, 19 Jul 2022 at 11:13, Marco Falke wrote: > > Thanks Jonathan. Either name is perfectly fine. OK, thanks. > > To clarify, this will be pushed to master and also backported to the 12-branch? Yes, that's right. It will go to trunk (aka master) today and then backported to the gcc-12 branch "soon" (whenever I do the next batch of backports, which might be later this week).