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.1 required=3.0 tests=AWL,BAYES_00,BODY_8BITS, 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 AF1B21F910 for ; Wed, 16 Nov 2022 06:52:56 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="BHCWFcxD"; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231686AbiKPGwy (ORCPT ); Wed, 16 Nov 2022 01:52:54 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58316 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231428AbiKPGwn (ORCPT ); Wed, 16 Nov 2022 01:52:43 -0500 Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E3FC628707 for ; Tue, 15 Nov 2022 22:52:41 -0800 (PST) Received: by mail-lj1-x22d.google.com with SMTP id d3so20613327ljl.1 for ; Tue, 15 Nov 2022 22:52:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=eACEQElCHuw15Ai6MII1LaDtP+9yIB6ARX5qtbDdlVE=; b=BHCWFcxDKWL95XLzqmACRlgpiS7bWwPkFibrscrxwc6tLBdWF3lxRCVWmD43nz3kLg uTQ3j+eAmghxVUQXRYKhr0vLmHS5UJoAySwZO3P0gCtUZVGvoLZ+eb6ACeIT+Xavw2qw rtJYEEHS2PdZYaClHn7TqpsfFPjUTyDi1bwtJucodYZSjCdqqoFsoRYPi26B4zpVh3mi CFBwyl/crMLIB+KvXMjBne+SjR3gvShmp3R5nFUSLnqZMgro3FNpidQX+5LIa4Lc3AGQ dgyXyFXuMDgwjVWowN01iHNS3QaKwP/adEfURMOzTWtZx0/LeSgUKrIQpCgs6fYIx0U5 DQJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=eACEQElCHuw15Ai6MII1LaDtP+9yIB6ARX5qtbDdlVE=; b=as0WyRJbxYWljNiugb97EBJPmrfhFZFms1/xyXTaW6CDZYCpYF8x9LqrfFjqa2/8A8 Sz1eAYLx86x6XAYkEwKhT8k+UmtM0oZx7T0tZS7gG87V5qA0kYTaeAH2ArlWOtu/MZmD nxu7+9b6K746VpkBaNn5xvs4f/tVd98AK01qWvnoy4/KROEXcfG/GIdM4sIWp8IMizoQ pvaPNGAB+pn8vLFROuoeXUoPOBzKM765Ap++6sVkB8VToSzo8C2k4YJP4FHBBliEaUpn ShFE4GOxJkq//ZeBbi/vgXjEPiI0LtQtWop468D+yXnQLnS8Z1N++/6m8MBV8vxDqNyZ wJkw== X-Gm-Message-State: ANoB5pnxbqm7Sn5jI3+RfF3Rygtpp7x8yJ6gLCJClF6QGRjYVU7zliMh 9C2zThaXBfaUwDlB3FJV8UdPCtUGfdt+nECI0Ds= X-Google-Smtp-Source: AA0mqf7W95zBiOfk2Kc5PadSdGLX6lWbFRFybGB/I4heJ9eB00a166wk++kESZ9PKHmtRckzIpu1nD//owCsWM0bCXg= X-Received: by 2002:a2e:8e2b:0:b0:278:f572:c9ac with SMTP id r11-20020a2e8e2b000000b00278f572c9acmr6474854ljk.73.1668581560123; Tue, 15 Nov 2022 22:52:40 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Elijah Newren Date: Tue, 15 Nov 2022 22:51:00 -0800 Message-ID: Subject: Re: [PATCH v4] sparse-checkout.txt: new document with sparse-checkout directions To: ZheNing Hu Cc: Elijah Newren via GitGitGadget , git@vger.kernel.org, Victoria Dye , Derrick Stolee , Shaoxuan Yuan , Matheus Tavares , Glen Choo , Martin von Zweigbergk Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Tue, Nov 15, 2022 at 7:18 PM ZheNing Hu wrote: > ZheNing Hu =E4=BA=8E2022=E5=B9=B411=E6=9C=8815= =E6=97=A5=E5=91=A8=E4=BA=8C 12:03=E5=86=99=E9=81=93=EF=BC=9A > > Elijah Newren via GitGitGadget =E4=BA=8E2022= =E5=B9=B411=E6=9C=886=E6=97=A5=E5=91=A8=E6=97=A5 14:04=E5=86=99=E9=81=93=EF= =BC=9A [...] > > > +sparse specification: The set of paths in the user's area of focus. = This > > > + is typically just the tracked files that match the sparsity > > > + patterns, but the sparse specification can temporarily differ= and > > > + include additional files. (See also "Sparse specification > > > + vs. sparsity patterns") > > > + > > > + * When working with history, the sparse specification is exac= tly > > > + the set of files matching the sparsity patterns. > > > + * When interacting with the working tree, the sparse specific= ation > > > + is the set of tracked files with a clear SKIP_WORKTREE bit = or > > > + tracked files present in the working copy. > > > > I found af6a518 (repo_read_index: clear SKIP_WORKTREE bit from files > present in worktree) Yes, that was one of the footnotes referenced in the file: +[3] (Present-despite-skipped entries) + https://lore.kernel.org/git/11d46a399d26c913787b704d2b7169cafc28d639.1= 642175983.git.gitgitgadget@gmail.com/ > which maybe a good place to learn about "sparse specification", > it has a long commit message though. Not quite; it was a predecessor that described some of the bugs caused by the facts that: * "SKIP_WORKTREE" meant the file would be missing from the worktree * the above promise was often violated in a variety of ways Experience with all the bugs caused by this situation (and the many other attempted workarounds we tried that kept falling short) certainly informed my suggestions about the sparse specification. However, that only looks at the working tree side; the sparse specification is also expanded for index-related operations, as I called out in the other email I just sent you.