On 10/18/2019 12:07 PM, SZEDER Gábor wrote: > On Tue, Oct 15, 2019 at 01:55:48PM +0000, Derrick Stolee via GitGitGadget > wrote: >> From: Derrick Stolee <dsto...@microsoft.com> >> >> The sparse-checkout feature is mostly hidden to users, as its >> only documentation is supplementary information in the docs for >> 'git read-tree'. In addition, users need to know how to edit the >> .git/info/sparse-checkout file with the right patterns, then run >> the appropriate 'git read-tree -mu HEAD' command. Keeping the >> working directory in sync with the sparse-checkout file requires >> care. >> >> Begin an effort to make the sparse-checkout feature a porcelain >> feature by creating a new 'git sparse-checkout' builtin. This >> builtin will be the preferred mechanism for manipulating the >> sparse-checkout file and syncing the working directory. >> >> The documentation provided is adapted from the "git read-tree" >> documentation with a few edits for clarity in the new context. >> Extra sections are added to hint toward a future change to >> a more restricted pattern set. >> >> Helped-by: Elijah Newren <new...@gmail.com> >> Signed-off-by: Derrick Stolee <dsto...@microsoft.com> >> --- >> .gitignore | 1 + >> Documentation/git-read-tree.txt | 2 +- >> Documentation/git-sparse-checkout.txt | 87 +++++++++++++++++++++++++++ >> Makefile | 1 + >> builtin.h | 1 + >> builtin/sparse-checkout.c | 86 ++++++++++++++++++++++++++ >> git.c | 1 + >> t/t1091-sparse-checkout-builtin.sh | 50 +++++++++++++++ > > You need to add an entry for the new command to 'command-list.txt' as > well, so it will be included in 'git help -a' and completion (since > it's intended to be a porcelain), etc. > >> 8 files changed, 228 insertions(+), 1 deletion(-) >> create mode 100644 Documentation/git-sparse-checkout.txt >> create mode 100644 builtin/sparse-checkout.c >> create mode 100755 t/t1091-sparse-checkout-builtin.sh > > >> diff --git a/Documentation/git-sparse-checkout.txt >> b/Documentation/git-sparse-checkout.txt >> new file mode 100644 >> index 0000000000..46d3dc3cb1 >> --- /dev/null >> +++ b/Documentation/git-sparse-checkout.txt >> @@ -0,0 +1,87 @@ >> +git-sparse-checkout(1) >> +======================= > > The ==== line is one character longer than the title; I think their > length should match. The other day the Documentation CI job failed > because the length of these lines didn't match in one of the guides. > Strangely, it doesn't complain about this one.
Interesting. GitGitGadget runs a documentation build, and it has never failed for me. Will fix. >> + >> +NAME >> +---- >> +git-sparse-checkout - Initialize and modify the sparse-checkout >> +configuration, which reduces the checkout to a set of directories >> +given by a list of prefixes. >> + >> + >> +SYNOPSIS >> +-------- >> +[verse] >> +'git sparse-checkout <subcommand> [options]' >> + >> + >> +DESCRIPTION >> +----------- >> + >> +Initialize and modify the sparse-checkout configuration, which reduces >> +the checkout to a set of directories given by a list of prefixes. >> + >> +THIS COMMAND IS EXPERIMENTAL. THE BEHAVIOR MAY CHANGE. >> + >> + >> +COMMANDS >> +-------- >> +'list':: >> + Provide a list of the contents in the sparse-checkout file. >> + >> + >> +SPARSE CHECKOUT >> +---------------- > > This is longer as well. > >> + >> +"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. >> + >> +## 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 >> +---------------- >> + >> +Another tricky thing is fully repopulating the working directory when you >> +no longer want sparse checkout. You cannot just disable "sparse >> +checkout" because skip-worktree bits are still in the index and your working >> +directory is still sparsely populated. You should re-populate the working >> +directory with the `$GIT_DIR/info/sparse-checkout` file content as >> +follows: >> + >> +---------------- >> +/* >> +---------------- >> + >> +Then you can disable sparse checkout. Sparse checkout support in 'git >> +checkout' and similar commands is disabled by default. You need to >> +set `core.sparseCheckout` to `true` in order to have sparse checkout >> +support. >> + >> +SEE ALSO >> +-------- >> + >> +linkgit:git-read-tree[1] >> +linkgit:gitignore[5] >> + >> +GIT >> +--- >> +Part of the linkgit:git[1] suite > >> diff --git a/t/t1091-sparse-checkout-builtin.sh >> b/t/t1091-sparse-checkout-builtin.sh >> new file mode 100755 >> index 0000000000..a9b04b1a88 >> --- /dev/null >> +++ b/t/t1091-sparse-checkout-builtin.sh >> @@ -0,0 +1,50 @@ >> +#!/bin/sh >> + >> +test_description='sparse checkout builtin tests' >> + >> +. ./test-lib.sh >> + >> +test_expect_success 'setup' ' >> + git init repo && >> + ( >> + cd repo && >> + echo "initial" >a && >> + mkdir folder1 folder2 deep && >> + mkdir deep/deeper1 deep/deeper2 && >> + mkdir deep/deeper1/deepest && >> + cp a folder1 && >> + cp a folder2 && >> + cp a deep && >> + cp a deep/deeper1 && >> + cp a deep/deeper2 && >> + cp a deep/deeper1/deepest && > > There are six 'cp' invocations here. Curious: does this mean that > it's important that all those files are the same? The content of the "a" file is not important at all to the tests. It only matters that there is a blob in each of these trees. > >> + git add . && >> + git commit -m "initial commit" >> + ) >> +' >> + >> +test_expect_success 'git sparse-checkout list (empty)' ' >> + git -C repo sparse-checkout list >list 2>err && >> + test_line_count = 0 list && > > Nit: test_must_be_empty might be a bit more idiomatic, dunno. > >> + test_i18ngrep "this worktree is not sparse (sparse-checkout file may >> not exist)" err >> +' >> + >> +test_expect_success 'git sparse-checkout list (populated)' ' >> + test_when_finished rm -f repo/.git/info/sparse-checkout && >> + cat >repo/.git/info/sparse-checkout <<-EOF && >> + /folder1/* >> + /deep/ >> + **/a >> + !*bin* >> + EOF >> + git -C repo sparse-checkout list >list && >> + cat >expect <<-EOF && >> + /folder1/* >> + /deep/ >> + **/a >> + !*bin* >> + EOF > > OTOH, here the content of the 'sparse-checkout' file and 'expect' must > be the same, but one has to carefully look through four lines of > patterns to realize that they are indeed the same. I think in this > case the explicitness of 'cp' would be better. That's fine. We explicitly set the contents in the line above. >> + test_cmp expect list >> +' >> + >> +test_done >> -- >> gitgitgadget >>
