-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Management of sparsely checked-out working tree has gained a dedicated "sparse-checkout" command. * ds/sparse-cone: (21 commits) sparse-checkout: improve OS ls compatibility sparse-checkout: respect core.ignoreCase in cone mode sparse-checkout: check for dirty status sparse-checkout: update working directory in-process for 'init' sparse-checkout: cone mode should not interact with .gitignore sparse-checkout: write using lockfile sparse-checkout: use in-process update for disable subcommand sparse-checkout: update working directory in-process sparse-checkout: sanitize for nested folders unpack-trees: add progress to clear_ce_flags() unpack-trees: hash less in cone mode sparse-checkout: init and set in cone mode sparse-checkout: use hashmaps for cone patterns sparse-checkout: add 'cone' mode trace2: add region in clear_ce_flags sparse-checkout: create 'disable' subcommand sparse-checkout: add '--stdin' option to set subcommand sparse-checkout: 'set' subcommand clone: add --sparse mode sparse-checkout: create 'init' subcommand ...
- Loading branch information
Showing
20 changed files
with
1,376 additions
and
48 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,166 @@ | ||
git-sparse-checkout(1) | ||
====================== | ||
|
||
NAME | ||
---- | ||
git-sparse-checkout - Initialize and modify the sparse-checkout | ||
configuration, which reduces the checkout to a set of paths | ||
given by a list of atterns. | ||
|
||
|
||
SYNOPSIS | ||
-------- | ||
[verse] | ||
'git sparse-checkout <subcommand> [options]' | ||
|
||
|
||
DESCRIPTION | ||
----------- | ||
|
||
Initialize and modify the sparse-checkout configuration, which reduces | ||
the checkout to a set of paths given by a list of patterns. | ||
|
||
THIS COMMAND IS EXPERIMENTAL. ITS BEHAVIOR, AND THE BEHAVIOR OF OTHER | ||
COMMANDS IN THE PRESENCE OF SPARSE-CHECKOUTS, WILL LIKELY CHANGE IN | ||
THE FUTURE. | ||
|
||
|
||
COMMANDS | ||
-------- | ||
'list':: | ||
Provide a list of the contents in the sparse-checkout file. | ||
|
||
'init':: | ||
Enable the `core.sparseCheckout` setting. If the | ||
sparse-checkout file does not exist, then populate it with | ||
patterns that match every file in the root directory and | ||
no other directories, then will remove all directories tracked | ||
by Git. Add patterns to the sparse-checkout file to | ||
repopulate the working directory. | ||
+ | ||
To avoid interfering with other worktrees, it first enables the | ||
`extensions.worktreeConfig` setting and makes sure to set the | ||
`core.sparseCheckout` setting in the worktree-specific config file. | ||
|
||
'set':: | ||
Write a set of patterns to the sparse-checkout file, as given as | ||
a list of arguments following the 'set' subcommand. Update the | ||
working directory to match the new patterns. Enable the | ||
core.sparseCheckout config setting if it is not already enabled. | ||
+ | ||
When the `--stdin` option is provided, the patterns are read from | ||
standard in as a newline-delimited list instead of from the arguments. | ||
|
||
'disable':: | ||
Disable the `core.sparseCheckout` config setting, and restore the | ||
working directory to include all files. Leaves the sparse-checkout | ||
file intact so a later 'git sparse-checkout init' command may | ||
return the working directory to the same state. | ||
|
||
SPARSE CHECKOUT | ||
--------------- | ||
|
||
"Sparse checkout" allows populating the working directory sparsely. | ||
It uses the skip-worktree bit (see linkgit:git-update-index[1]) to tell | ||
Git whether a file in the working directory is worth looking at. If | ||
the skip-worktree bit is set, then the file is ignored in the working | ||
directory. Git will not populate the contents of those files, which | ||
makes a sparse checkout helpful when working in a repository with many | ||
files, but only a few are important to the current user. | ||
|
||
The `$GIT_DIR/info/sparse-checkout` file is used to define the | ||
skip-worktree reference bitmap. When Git updates the working | ||
directory, it updates the skip-worktree bits in the index based | ||
on this file. The files matching the patterns in the file will | ||
appear in the working directory, and the rest will not. | ||
|
||
To enable the sparse-checkout feature, run `git sparse-checkout init` to | ||
initialize a simple sparse-checkout file and enable the `core.sparseCheckout` | ||
config setting. Then, run `git sparse-checkout set` to modify the patterns in | ||
the sparse-checkout file. | ||
|
||
To repopulate the working directory with all files, use the | ||
`git sparse-checkout disable` command. | ||
|
||
|
||
FULL PATTERN SET | ||
---------------- | ||
|
||
By default, the sparse-checkout file uses the same syntax as `.gitignore` | ||
files. | ||
|
||
While `$GIT_DIR/info/sparse-checkout` is usually used to specify what | ||
files are included, you can also specify what files are _not_ included, | ||
using negative patterns. For example, to remove the file `unwanted`: | ||
|
||
---------------- | ||
/* | ||
!unwanted | ||
---------------- | ||
|
||
|
||
CONE PATTERN SET | ||
---------------- | ||
|
||
The full pattern set allows for arbitrary pattern matches and complicated | ||
inclusion/exclusion rules. These can result in O(N*M) pattern matches when | ||
updating the index, where N is the number of patterns and M is the number | ||
of paths in the index. To combat this performance issue, a more restricted | ||
pattern set is allowed when `core.spareCheckoutCone` is enabled. | ||
|
||
The accepted patterns in the cone pattern set are: | ||
|
||
1. *Recursive:* All paths inside a directory are included. | ||
|
||
2. *Parent:* All files immediately inside a directory are included. | ||
|
||
In addition to the above two patterns, we also expect that all files in the | ||
root directory are included. If a recursive pattern is added, then all | ||
leading directories are added as parent patterns. | ||
|
||
By default, when running `git sparse-checkout init`, the root directory is | ||
added as a parent pattern. At this point, the sparse-checkout file contains | ||
the following patterns: | ||
|
||
---------------- | ||
/* | ||
!/*/ | ||
---------------- | ||
|
||
This says "include everything in root, but nothing two levels below root." | ||
If we then add the folder `A/B/C` as a recursive pattern, the folders `A` and | ||
`A/B` are added as parent patterns. The resulting sparse-checkout file is | ||
now | ||
|
||
---------------- | ||
/* | ||
!/*/ | ||
/A/ | ||
!/A/*/ | ||
/A/B/ | ||
!/A/B/*/ | ||
/A/B/C/ | ||
---------------- | ||
|
||
Here, order matters, so the negative patterns are overridden by the positive | ||
patterns that appear lower in the file. | ||
|
||
If `core.sparseCheckoutCone=true`, then Git will parse the sparse-checkout file | ||
expecting patterns of these types. Git will warn if the patterns do not match. | ||
If the patterns do match the expected format, then Git will use faster hash- | ||
based algorithms to compute inclusion in the sparse-checkout. | ||
|
||
If `core.ignoreCase=true`, then the pattern-matching algorithm will use a | ||
case-insensitive check. This corrects for case mismatched filenames in the | ||
'git sparse-checkout set' command to reflect the expected cone in the working | ||
directory. | ||
|
||
SEE ALSO | ||
-------- | ||
|
||
linkgit:git-read-tree[1] | ||
linkgit:gitignore[5] | ||
|
||
GIT | ||
--- | ||
Part of the linkgit:git[1] suite |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.