Hi,
Nguyễn Thái Ngọc Duy wrote:
> --- a/Documentation/git-checkout.txt
> +++ b/Documentation/git-checkout.txt
> @@ -180,6 +180,13 @@ branch by running "git rm -rf ." from the top level of
> the working tree.
> Afterwards you will be ready to prepare your new files, repopulating the
> working tree, by copying them from elsewhere, extracting a tarball, etc.
>
> +
> +--sparse::
> + In sparse checkout mode, `git checkout -- <paths>` would
> + update all entries matched by <paths> regardless sparse
> + patterns. This option only updates entries matched by <paths>
> + and sparse patterns.
Hm, should this be the default?
In principle, I would expect
git checkout -- .
to make the worktree match the index, respecting the sparse checkout.
And something like
git checkout --widen -- .
to change the sparse checkout pattern. But of course it is easily
possible that I am missing some details of how sparse checkout is
used in practice.
What do you think?
Jonathan
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
