Re: Make "git clone" less of a deathly quiet experience

Linus Torvalds [off-list ref] writes:

Btw, we should print out the other "stages" too - the checkout in 
particular can be a big part of the overhead, and it would probably make 
sense to tell people about the fact that "hey, now we're checking the 
result out, we're not actually trying to destroy your disk".

Would you suggest doing that with "checkout-index -v", that
shows "1 path1\r2 path2\r3 path3\r...\rDone.\n"?

On Fri, 10 Feb 2006, Junio C Hamano wrote:

Would you suggest doing that with "checkout-index -v", that
shows "1 path1\r2 path2\r3 path3\r...\rDone.\n"?

Not if it shows every single path.

When going tty output, we should be careful to limit it to not do tons and 
tons of lines. The download output does gettimeofday to limit itself to 
max 2 times per sec, and the percentage output of git-unpack-objects 
similarly limits itself so that it never spews _tons_ of stuff to the 
terminal.

Under many loads, the terminal will be a lot slower than actually writing 
a file ("context switch to gnome-term + context switch to X + set up 
complex text output").

		Linus