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: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id 53ED01F45E for ; Tue, 11 Feb 2020 17:06:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728644AbgBKRGm (ORCPT ); Tue, 11 Feb 2020 12:06:42 -0500 Received: from pb-smtp2.pobox.com ([64.147.108.71]:53330 "EHLO pb-smtp2.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728288AbgBKRGm (ORCPT ); Tue, 11 Feb 2020 12:06:42 -0500 Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 43B60429C7; Tue, 11 Feb 2020 12:06:41 -0500 (EST) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=Z7+ESFqJs0lOk1A0kQJ7G7JFBG8=; b=Uyvk5Z p1CVeOuBEooJL1t9LJvi62ZG8gh8pSSOK4nQtesA4Ao9skuermgbMy7NHn6QBfQP wvabSCm41O2ynxUwUVHXcG+43dgTYUsfByS4d22ZB9HBWaRUVvgDamL56o3DYao7 oZzMCasSa7OuvWjvFmGcbUAZQ922xWAsCD4Tc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=HHSntxmLmtGFXbzLmHFlyktKLw7RtkQi AeCPiSmPL/YyhH1jqHg60NlAljSxoUJobmAMmmK0MjfIZrvzZWaisBLtpXeF1w81 Nco+0Qub8qsmtrnfn7H3s2WOXehyoGUyUwBvni3u0NtXrMPQsZpLZ0gsGSvqK5CM qQVTPaUrAw8= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 3C121429C6; Tue, 11 Feb 2020 12:06:41 -0500 (EST) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [34.76.80.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 988A4429C5; Tue, 11 Feb 2020 12:06:40 -0500 (EST) (envelope-from junio@pobox.com) From: Junio C Hamano To: "Derrick Stolee via GitGitGadget" Cc: git@vger.kernel.org, me@ttaylorr.com, peff@peff.net, newren@gmail.com, Derrick Stolee Subject: Re: [PATCH 0/4] Sparse-checkout: Add subcommand and Windows paths References: Date: Tue, 11 Feb 2020 09:06:39 -0800 In-Reply-To: (Derrick Stolee via GitGitGadget's message of "Tue, 11 Feb 2020 15:02:20 +0000") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: DF101EDC-4CF0-11EA-9A45-D1361DBA3BAF-77302942!pb-smtp2.pobox.com Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org "Derrick Stolee via GitGitGadget" writes: > This is based on ds/sparse-checkout-harden. > > The sparse-checkout builtin currently lets users modify their > sparse-checkout file with the all-or-nothing "set" subcommand. It may be > easier for a user to expand their sparse cone using a "git sparse-checkout > add ..." subcommand. Makes sense. I suspect that people may get greedy and start saying "now we can add a new directory (say, Documentation/) without repeating what we already configured, I want a way to add a new directory without some of the paths in that directory (say, Documentation/ but not Documentation/technical/)", but that won't happen until people can use "add", so let's take small incremental steps, and addition of "add" is such a good first step. Will queue. Thanks.