mirror of
https://github.com/git/git.git
synced 2026-01-10 01:56:42 +00:00
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>
This commit is contained in:
committed by
Junio C Hamano
parent
5b5a7f5ebd
commit
66c11bd46a
@@ -32,7 +32,8 @@ int give_advice_on_expansion = 1;
|
|||||||
"Your working directory likely has contents that are outside of\n" \
|
"Your working directory likely has contents that are outside of\n" \
|
||||||
"your sparse-checkout patterns. Use 'git sparse-checkout list' to\n" \
|
"your sparse-checkout patterns. Use 'git sparse-checkout list' to\n" \
|
||||||
"see your sparse-checkout definition and compare it to your working\n" \
|
"see your sparse-checkout definition and compare it to your working\n" \
|
||||||
"directory contents. Running 'git clean' may assist in this cleanup."
|
"directory contents. Running 'git sparse-checkout clean' may assist\n" \
|
||||||
|
"in this cleanup."
|
||||||
|
|
||||||
struct modify_index_context {
|
struct modify_index_context {
|
||||||
struct index_state *write;
|
struct index_state *write;
|
||||||
|
|||||||
Reference in New Issue
Block a user