Re: What's cooking in git.git (Sep 2021, #04; Mon, 13)

From: Derrick Stolee <stolee@gmail.com>
Date: Sep 14, 2021, 13:33 UTC
Message-ID: <88bb51c3-b5ab-77df-f9fb-b9252c2b0fa6@gmail.com>
In-Reply-To: <xmqqtuinc3tx.fsf@gitster.g>

On 9/13/2021 10:02 PM, Junio C Hamano wrote: ...

Show 19 quoted lines

> * ds/add-rm-with-sparse-index (2021-09-12) 14 commits
>  - advice: update message to suggest '--sparse'
>  - mv: refuse to move sparse paths
>  - rm: skip sparse paths with missing SKIP_WORKTREE
>  - rm: add --sparse option
>  - add: update --renormalize to skip sparse paths
>  - add: update --chmod to skip sparse paths
>  - add: implement the --sparse option
>  - add: skip tracked paths outside sparse-checkout cone
>  - add: fail when adding an untracked sparse file
>  - dir: fix pattern matching on dirs
>  - dir: select directories correctly
>  - dir: extract directory-matching logic
>  - t1092: behavior for adding sparse files
>  - t3705: test that 'sparse_entry' is unstaged
>  (this branch uses ds/mergies-with-sparse-index and ds/sparse-index-ignored-files.)
> 
>  "git add", "git mv", and "git rm" have been adjusted to work better
>  with the sparse index.

These changes apply more generally to the entire sparse-checkout feature. I can understand thinking it is only related to the sparse index because the tests follow the sparse index patterns. Those tests make sure that both full and sparse indexes are tested and have the same behavior.

Perhaps this would be a good summary?

  "git add", "git mv", and "git rm" have been adjusted to avoid
  updating paths outside of the sparse-checkout definition unless
  the user specifies a "--sparse" option.

Thanks, -Stolee