Re: [PATCH 1/1] reset: fix reset when using the sparse-checkout feature.

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 11, 2017, 04:01 UTC
Message-ID: <xmqqh8w951ek.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <SN1PR21MB00140C84DC02F3491F4E8469B76A0@SN1PR21MB0014.namprd21.prod.outlook.com>

Kevin Willford <kewillf@microsoft.com> writes:

Show 7 quoted lines

> I agree with this when you are not dealing with a sparse-checkout.
> When using a sparse-checkout I expect git not to touch things
> outside of what I have specified in my sparse-checkout file.  If it
> does, it should let me know or put my working directory in a
> state that is expected.  Especially when it is changing the
> skip-worktree bits causing files outside the sparse-checkout to be
> reported incorrectly by status.

Well, whether using a sparse-checkout or not, I would expect Git not to touch *any* filesystem entity when "git reset" (not "--hard", just "git reset [<tree-ish>]") is given, whether the path is inside or outside the sparse-checkout area.

Stepping back a bit, I am not sure if it is sane or even valid for the end-user to modify paths outside sparse-checkout area, but that is probably a separate tangent.