summaryrefslogtreecommitdiff
path: root/git.c
diff options
context:
space:
mode:
authorNicolas Pitre <nico@fluxnic.net>2009-11-11 22:24:42 (GMT)
committerJunio C Hamano <gitster@pobox.com>2009-11-13 22:39:25 (GMT)
commit6b59f51b312f06d9420d34c09fa408c658aac6d2 (patch)
tree3dff3f5acea4ae259283b6fa1c3fda03336f263c /git.c
parent1b19fa46344f512949270dc88089574950519ea3 (diff)
downloadgit-6b59f51b312f06d9420d34c09fa408c658aac6d2.zip
git-6b59f51b312f06d9420d34c09fa408c658aac6d2.tar.gz
git-6b59f51b312f06d9420d34c09fa408c658aac6d2.tar.bz2
give priority to progress messages
In theory it is possible for sideband channel #2 to be delayed if pack data is quick to come up for sideband channel #1. And because data for channel #2 is read only 128 bytes at a time while pack data is read 8192 bytes at a time, it is possible for many pack blocks to be sent to the client before the progress message fifo is emptied, making the situation even worse. This would result in totally garbled progress display on the client's console as local progress gets mixed with partial remote progress lines. Let's prevent such situations by giving transmission priority to progress messages over pack data at all times. Signed-off-by: Nicolas Pitre <nico@fluxnic.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git.c')
0 files changed, 0 insertions, 0 deletions