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: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.9 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by dcvr.yhbt.net (Postfix) with ESMTP id 8E3001F4D7 for ; Mon, 20 Jun 2022 23:17:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345964AbiFTXRj (ORCPT ); Mon, 20 Jun 2022 19:17:39 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37326 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1347341AbiFTXRF (ORCPT ); Mon, 20 Jun 2022 19:17:05 -0400 Received: from elephants.elehost.com (elephants.elehost.com [216.66.27.132]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 81F3127B2C for ; Mon, 20 Jun 2022 16:13:20 -0700 (PDT) Received: from Mazikeen (cpe00fc8d49d843-cm00fc8d49d840.cpe.net.cable.rogers.com [174.119.96.21] (may be forged)) (authenticated bits=0) by elephants.elehost.com (8.16.1/8.16.1) with ESMTPSA id 25KNDIVU074230 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 20 Jun 2022 19:13:18 -0400 (EDT) (envelope-from rsbecker@nexbridge.com) Reply-To: From: To: "'Stephen Smith'" , "'git'" References: <12011256.O9o76ZdvQC@thunderbird> In-Reply-To: <12011256.O9o76ZdvQC@thunderbird> Subject: RE: SHA-256 transition Date: Mon, 20 Jun 2022 19:13:12 -0400 Organization: Nexbridge Inc. Message-ID: <00e601d884fb$53ccfb70$fb66f250$@nexbridge.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Content-Language: en-ca Thread-Index: AQKdzPESrq0KdVHDZKCsGYSrLnv73qvOXI2Q Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On June 20, 2022 6:51 PM, Stephen Smith wrote: >What is the current status of the SHA-1 to SHA-256 transition? Is the >transition far enough along that users should start changing over to the new >format? I had the same question at a conference last week. Could not answer it so am curious about the plan.