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.6 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,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 2071D1F54E for ; Wed, 24 Aug 2022 11:35:26 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="P3L04wJZ"; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236646AbiHXLem (ORCPT ); Wed, 24 Aug 2022 07:34:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56472 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235571AbiHXLel (ORCPT ); Wed, 24 Aug 2022 07:34:41 -0400 Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 85EFE8284F for ; Wed, 24 Aug 2022 04:34:37 -0700 (PDT) Received: by mail-ej1-x62d.google.com with SMTP id y3so6567727ejc.1 for ; Wed, 24 Aug 2022 04:34:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=5U8a1rZMStEgC/xmttkZDHOX599lR1jw5FFVw48kvwc=; b=P3L04wJZdm1yt9yYKagEDQbV63OYa1gEBN/PfZmoFqw0T1xJQRfhowe3vjrygTv458 myHey3D1PpZSjuXVGt8MOFM2bcZCzT39j7wJf0//WUVM5hsyFORCsNF/odnZcrj5StDf lFX0GABo7MdUnDtPq7B6PE5e+mSZTcHaFu15Nn5REO05/nojtufUe2iWhM0T5mNHLZVL OQvOPDqnpKbP87tzmK7f36N97DpZGz3vjEdqW0M2WfjpPnS7lmZfSWqQcwn5ZLEg1KWE kRc6shGHMCyFWhlKFl/2u0VU8nTlVBqC5o9tPgp+OcPJo+9PctVhj0Huva+hdYagAJ0b SbqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=5U8a1rZMStEgC/xmttkZDHOX599lR1jw5FFVw48kvwc=; b=V6SxQX1AEMXd9LJaBSmP4KS7swSdCoejYN7nwf68AsGthkU5QkGmlNRypYMWPQLAjJ 32arDh44fwOBXhi+Ht1ct5flRbXLNTSHfIhbMnUhx4nZ4fkvAbr7XpLLpBdkWFXn5XdK 26N5agghGSg4E836FYzqamOicdTFhPl53voKDUBdSLcAFNcsK88tRzbKRpSn7EYVmYVb pr5O/gdJc1JYzem4uckTXWok5P7Q5fvN+b6hiQg3QfOVQowaGdx7wEtrJADXai2jWIAn i1BR+lmNeAserJ8lIm6qIIsxZptAnE7fVlkvU7TOfJsqvlUenI755+0YI6+ZZrFkzbls WT0w== X-Gm-Message-State: ACgBeo3pRJJ+KUzVMVxc9o64hDxXkLybfX1890DXYqNaZmvuP4qTXXpF Mr1YQD0PwTh/Cm6L5FuSg5NjRZQEvEyBQ/knWec= X-Google-Smtp-Source: AA6agR7TiplCfW8QY2j0G+nZot45QlLjdtn4tqTF2c7w6dpKNtbVuNGordGyoef/UJQDQw/xLNkAofL4ubIA0g11EBw= X-Received: by 2002:a17:907:2da4:b0:731:2772:59d9 with SMTP id gt36-20020a1709072da400b00731277259d9mr2654480ejc.751.1661340876073; Wed, 24 Aug 2022 04:34:36 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Jinwook Jeong Date: Wed, 24 Aug 2022 20:34:19 +0900 Message-ID: Subject: Re: bugreport: "git config --global" fails if an invalid .git file present To: Jeff King Cc: Junio C Hamano , git@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Thu, Aug 18, 2022 at 3:16 PM Jeff King wrote: > I agree this isn't entirely friendly, but I think things are working as > designed. Even though you're only asking to change global config, we do > still speculatively check for a repository when running git-config at > all, as various options could impact its behavior. So the backtrace > looks like this: I didn't know that a local repository could affect the result of "git config --global". Thank you for the detailed explanation!