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: AS53758 23.128.96.0/24 X-Spam-Status: No, score=-3.5 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,NICE_REPLY_A, RCVD_IN_DNSWL_MED,RCVD_IN_SORBS_WEB,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id 0A6E01F8C8 for ; Wed, 6 Oct 2021 10:33:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238047AbhJFKfM (ORCPT ); Wed, 6 Oct 2021 06:35:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38850 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237836AbhJFKfM (ORCPT ); Wed, 6 Oct 2021 06:35:12 -0400 Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 95388C061749 for ; Wed, 6 Oct 2021 03:33:20 -0700 (PDT) Received: by mail-pl1-x630.google.com with SMTP id a11so1429662plm.0 for ; Wed, 06 Oct 2021 03:33:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=xqx/ouvN/PO/2wj/IYyhY5hDvsZYJWiL6TeA7r9etH0=; b=kxvAR4QzmKxp4+vVZXlws26fLYriMGX6H6ZJADIPy1x2NhVSvwQhcQH1ngqaWil0pM dbmQ3aePv7jvm6y6lgWOajmiczHNcXQU/d9E2t4JpSdrol89fxwAyvcjJE7eq/ACTIqt PwcvOisTjCms5BOcwb+eL6cioGmpp6xJkB2VKqpsWwMk1VD8CLWoyBrtEokaC50z//Sz wawMfGx5oehR2rfrQdQMy5C82WBFl+Mncn5kFpZL4I+jxZ6D8EoPCmcXZ+T+jWBwubv/ 42sEiK61IajEbGZZC5VoIFvKpCbMatoke5t2qEFNNUHa7oLastXtl74KYBSyARd+Uy/P xfxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=xqx/ouvN/PO/2wj/IYyhY5hDvsZYJWiL6TeA7r9etH0=; b=Inu/UBP2LGii+DFjPL7znU0QfP8NvxH5KnXAPkQCaa0nZPxlINAyTIuKwQd1n6Jd9z IlDglZLj1nyRDZKlvoxo3DentDfGK6GH0NQ2Vd9N9Nk5ujPBVdpzo+OyhaMd80g7si8n I8VURn3mxFEuxvFls+5x79raRWXAZzUyeH7YcLalQreskx6NLHZTY/UnMAo3BNXNjMkD bqktKox6LsXcaT10JSWx1/vK5OFoSVJSiXr/X67q+GzK3un0SStJm22t6KpetyMkC5bs 4ojJTa0XKWuUt4jqigNYWRW1tHWVTOCdRPiqL+yR75nHsWVTduG6DWt+Nd5xT+bNjjZB L3nA== X-Gm-Message-State: AOAM530a+EJVtTcnSglufPMNaQGLD84LjHSHS2nNe3ZHhXCfZ6mH84DI HgfYUjv3Z/Bw1KeAtQUkAos= X-Google-Smtp-Source: ABdhPJzcnGSF7BoA4c0Ag9Kv/8BXu97s54RP6Lo5v3I4O4Po5p4yOIcSIl/baG5oUojkH3iu/61Ojw== X-Received: by 2002:a17:90a:4414:: with SMTP id s20mr9956878pjg.144.1633516399923; Wed, 06 Oct 2021 03:33:19 -0700 (PDT) Received: from [192.168.43.80] (subs03-180-214-233-73.three.co.id. [180.214.233.73]) by smtp.gmail.com with ESMTPSA id t9sm4757434pjm.36.2021.10.06.03.33.17 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Oct 2021 03:33:19 -0700 (PDT) Subject: Re: [PATCH v2 2/7] update-index: add --force-full-index option for expand/collapse test To: Victoria Dye via GitGitGadget , git@vger.kernel.org Cc: stolee@gmail.com, gitster@pobox.com, newren@gmail.com, Taylor Blau , Victoria Dye References: From: Bagas Sanjaya Message-ID: Date: Wed, 6 Oct 2021 17:33:16 +0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On 05/10/21 20.20, Victoria Dye via GitGitGadget wrote: > From: Victoria Dye > > Add a new `--force-full-index` option to `git update-index`, which skips > explicitly setting `command_requires_full_index`. This lets `git > update-index --force-full-index` run as a command without sparse index > compatibility implemented, even after it receives sparse index compatibility > updates. `... explicitly setting ...` or `... explicitly set ...`? I thought of the latter. -- An old man doll... just what I always wanted! - Clara