projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: f29ac4f) | patch
progress bar: round to the nearest instead of truncating down
authorNicolas Pitre <nico@cam.org>
Fri, 24 Apr 2009 21:46:15 +0000 (17:46 -0400)
committerJunio C Hamano <gitster@pobox.com>
Sat, 25 Apr 2009 15:54:18 +0000 (08:54 -0700)
commit66913284f06da58e2243acfad951a57501b8d813
treec6ba039d76ef1cc5318ff3b98e63fd2b9e057f85tree | snapshot
parentf29ac4f1b04c9cf84509e4a80f27f10b4373a446commit | diff
progress bar: round to the nearest instead of truncating down

Often the throughput output is requested when the data read so far is
one smaller than multiple of 1024; because 1023/1024 is ~0.999, it often
shows up as 0.99 because the code currently truncates.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
progress.c diff | blob | history
Git—the stupid content tracker