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

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 13, 2017, 22:17 UTC
Message-ID: <xmqqy3piz1j4.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CA+P7+xqcAh4v4gDQOm-feYGc1EmFztAu0zMg2xnp8Gn4=BzkoQ@mail.gmail.com>

Jacob Keller <jacob.keller@gmail.com> writes:

Show 6 quoted lines

> By definition if you do a sparse checkout, you're telling git "I only
> care about the files in this sparse checkout, and do not concern me
> with anything else"... So the proposed fix is "since git cleared the
> skip-worktree flag, we should actually also copy the file out again."
> but I think the real problem is that we're clearing skip worktree to
> begin with?

As this 100% agree with what I've been saying, I do not have anything to add to the discussion at the moment, so I'll stop speaking now but will continue to monitor the thread so that I may hear a new argument and datapoint that would make me change my mind.

Thanks for a healthy discussion.