Jacob Keller <jacob.keller@xxxxxxxxx> writes: > 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.
