Thread (4 messages) flat view 4 messages, 4 authors, 2016-06-15

Re: [PATCH] status: hint the user about -uno if read_directory takes too long

From: Duy Nguyen <hidden>
Date: 2016-06-15 22:56:24

Possibly related (same subject, not in this thread)

On Thu, Mar 14, 2013 at 10:05 PM, Junio C Hamano [off-list ref] wrote:
quoted
quoted
"to speed up by stopping displaying untracked files" does not look
like giving a balanced suggestion.  It is increasing the risk of
forgetting about newly created files the user may want to add, but
the risk is not properly warned.
How about "It took X ms to collect untracked files.\nCheck out the
option -u for a potential speedup"? I deliberately hide "no" so that
the user cannot blindly type and run it without reading document
first. We can give full explanation and warning there in the document.
But it makes the advise much less useful to introduce more levels of
indirections, no?
To me the message's value is the pointer to -uno that not many people
know about. And I don't want it to be too verbose as there'll be false
positives (cold cache, busy disks, low memory..), 2-3 lines should be
max. So indirections are not a concern. You want to speed up, you need
to pay some time. Anyway how do you put it to suggest -uno in
git-status with all the implications?
-- 
Duy
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help