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=-5.2 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A, 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 466591F4D7 for ; Sun, 15 May 2022 11:38:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236548AbiEOLiI (ORCPT ); Sun, 15 May 2022 07:38:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51874 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236547AbiEOLiG (ORCPT ); Sun, 15 May 2022 07:38:06 -0400 Received: from smtp.hosts.co.uk (smtp.hosts.co.uk [85.233.160.19]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8A5BE3B02A for ; Sun, 15 May 2022 04:38:04 -0700 (PDT) Received: from host217-43-165-125.range217-43.btcentralplus.com ([217.43.165.125] helo=[192.168.1.168]) by smtp.hosts.co.uk with esmtpa (Exim) (envelope-from ) id 1nqCZW-0000xd-BC; Sun, 15 May 2022 12:38:02 +0100 Message-ID: <7515c5df-a547-c4dc-5221-0f5089f2a2c3@iee.email> Date: Sun, 15 May 2022 12:38:01 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 Subject: Re: sudo: git describe during GIT_VERSION_GEN not as expected.. Content-Language: en-US To: Carlo Arenas Cc: Git List References: <7bb71920-b840-5133-ceac-664c09942772@iee.email> From: Philip Oakley In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Hi Carlo On 15/05/2022 12:05, Carlo Arenas wrote: > On Sun, May 15, 2022 at 3:12 AM Philip Oakley wrote: >> Is this a temporary position, as the sudo safe.directory problem is >> still to be added to next? > yes, it should be fixed once/if that branch graduates to next, and it > is currently broken in master and all maint branches as well as the > last 2 releases from those. > > Carlo Thanks for clarifying. Wasn't sure if it was finger trouble on my side. P.