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=-2.7 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 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 D442B1F51E for ; Wed, 28 Sep 2022 05:42:20 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="ojCMLvjz"; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232160AbiI1FmS (ORCPT ); Wed, 28 Sep 2022 01:42:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60660 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230185AbiI1FmQ (ORCPT ); Wed, 28 Sep 2022 01:42:16 -0400 Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 30A90FE671 for ; Tue, 27 Sep 2022 22:42:15 -0700 (PDT) Received: by mail-lj1-x232.google.com with SMTP id a10so13231687ljq.0 for ; Tue, 27 Sep 2022 22:42:15 -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:subject:date; bh=Zs9+hbGUW96eERlzcuPafzXgvREqWAEevqiugLi0UI8=; b=ojCMLvjzK+l7E4X8hrwNp/kbSHubCGVeu0kFJzXg3YUS1XJBMNGgzs5gagVYiij5iO dg9nD+yecmTM1/Yjsq8lVssQBExF4+TW3QLFyKzBGlkpFboa2tjG4R+04vL6/codW6jM aeZF6xFQGEBWTSlHPrwRQdi7xGEPhMD4nuqQ7MUNYng9uvyeU6PE4TSewOuAExNPXi9u DtUvMCoA7mEUhFHJi++G1qkAD9hIREGRRn6R5qSUPQHSAyNiqbNTeuxJUmhG6mByns95 KZT1qWJMvL4+ZLnjONEEUURf6Vr72WpEZ1RvApOlIPpQah2v5GnjORj+VkkCBCljm06E Gqdw== 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:subject:date; bh=Zs9+hbGUW96eERlzcuPafzXgvREqWAEevqiugLi0UI8=; b=pIu3FGpBDWsVmC+iPZDOo/0sUu8TuTVG9B9cFFAzXBZMMtH9tQ0A+eS7DjyDqAW94i 9AcuUb5E7BLN7s+EHt+mNr0D6y/WEFeqMOM5xQ5y2J7kWYkXCBe77Jrmg11HQ6OW9+Ff WhvCTrJmeSc2f6UdCzihklkNhpkEZfOf9xNVl6Iesw8q5fjfEoSpYq9tvdRRHgaTUmgk aJJ0X3lIkKXlR/GhrzzsjDTE0ZgNtOopJxaGIFXMHaQlelV+WP8TPZY/5ziTJYbeUT9S v9l5yuvvzujnpA3zdQQZ2pBOSxTcfyYvGeBfmqfPF/NaHSvyXxBH9cvGj4191RvtQhnj dgPw== X-Gm-Message-State: ACrzQf2gFIEdN0dLBcuJa1IURUvHXX7wEq59/NJbeIxuFKIpg+1bDVVb 54Sw9J/zCBDVY8u4ldG8xqlwE8siLozpFwH/aIzrhh1j X-Google-Smtp-Source: AMsMyM4Ngzb+0wxi/dSot+ka8tvsem9g0qYA6LX1rtL+KGC6fSBAWMqGU/wySc+iU2qDBZ3jhVQCHv8NxTRmXEGFUII= X-Received: by 2002:a2e:921a:0:b0:26c:1166:6666 with SMTP id k26-20020a2e921a000000b0026c11666666mr11266679ljg.128.1664343733569; Tue, 27 Sep 2022 22:42:13 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Elijah Newren Date: Tue, 27 Sep 2022 22:42:02 -0700 Message-ID: Subject: Re: [PATCH] sparse-checkout.txt: new document with sparse-checkout directions To: Derrick Stolee Cc: Victoria Dye , Elijah Newren via GitGitGadget , Git Mailing List , Shaoxuan Yuan , Matheus Tavares , ZheNing Hu Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Tue, Sep 27, 2022 at 9:42 AM Derrick Stolee wrote: > > On 9/26/2022 4:08 PM, Victoria Dye wrote: [...] > > 1. This could be a "me" problem, but I regularly struggle with "sparse" > > having different meanings in similar contexts. For example, a "sparse > > directory" is one *with* 'SKIP_WORKTREE' applied vs. "the sparse portion > > of the repo" here refers to the files *without* 'SKIP_WORKTREE' applied. > > A quick note/section outlining some standard terminology would be > > immensely helpful. > > This difference is absolutely my fault, and maybe we should consider > fixing this problem by renaming sparse directories something else. Hey now, don't reviewers also get some of the "credit"? ;-) > Perhaps "skipped directory" would be a better name? Sounds reasonable to me.