freshlybakedca.ke / git
Git fork
fork atom

sparse-index: point users to new 'clean' action

In my experience, the most-common reason that the sparse index must
expand to a full one is because there is some leftover file in a tracked
directory that is now outside of the sparse-checkout. The new 'git
sparse-checkout clean' command will find and delete these directories,
so point users to it when they hit the sparse index expansion advice.

Signed-off-by: Derrick Stolee <stolee@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>

authored by

Derrick Stolee and committed by
Junio C Hamano 66c11bd4 5b5a7f5e

+2 -1
unified split
+2 -1
sparse-index.c
··· 32 "Your working directory likely has contents that are outside of\n" \ 33 "your sparse-checkout patterns. Use 'git sparse-checkout list' to\n" \ 34 "see your sparse-checkout definition and compare it to your working\n" \ 35 - "directory contents. Running 'git clean' may assist in this cleanup." 36 37 struct modify_index_context { 38 struct index_state *write;
··· 32 "Your working directory likely has contents that are outside of\n" \ 33 "your sparse-checkout patterns. Use 'git sparse-checkout list' to\n" \ 34 "see your sparse-checkout definition and compare it to your working\n" \ 35 + "directory contents. Running 'git sparse-checkout clean' may assist\n" \ 36 + "in this cleanup." 37 38 struct modify_index_context { 39 struct index_state *write;