diff options
author | Junio C Hamano <gitster@pobox.com> | 2020-04-29 17:03:20 -0700 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2020-04-29 17:03:20 -0700 |
commit | 67cc2b7cdda7af3a7079b399a8a154d094efc649 (patch) | |
tree | 9c4830195de2ffd5ecdfca15e0e04be9bf959a4e /git-sparse-checkout.txt | |
parent | 0dd50943c112dfc70367bd39eb3c88371db2518f (diff) | |
download | git-htmldocs-67cc2b7cdda7af3a7079b399a8a154d094efc649.tar.gz |
Autogenerated HTML docs for v2.26.2-447-gd61d2
Diffstat (limited to 'git-sparse-checkout.txt')
-rw-r--r-- | git-sparse-checkout.txt | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/git-sparse-checkout.txt b/git-sparse-checkout.txt index c0342e539..1a3ace608 100644 --- a/git-sparse-checkout.txt +++ b/git-sparse-checkout.txt @@ -70,6 +70,16 @@ C-style quoted strings. `core.sparseCheckoutCone` is enabled, the given patterns are interpreted as directory names as in the 'set' subcommand. +'reapply:: + Reapply the sparsity pattern rules to paths in the working tree. + Commands like merge or rebase can materialize paths to do their + work (e.g. in order to show you a conflict), and other + sparse-checkout commands might fail to sparsify an individual file + (e.g. because it has unstaged changes or conflicts). In such + cases, it can make sense to run `git sparse-checkout reapply` later + after cleaning up affected paths (e.g. resolving conflicts, undoing + or committing changes, etc.). + 'disable':: Disable the `core.sparseCheckout` config setting, and restore the working directory to include all files. Leaves the sparse-checkout |