kernel/git - git - PowerEL Git System

Tree: 9d880582ee

Author	SHA1	Message	Date
Nicolas Pitre	9ac13ec941	atomic write for sideband remote messages It has been a few times that I ended up with such a confusing display: \|remote: Generating pack... \|remote: Done counting 17 objects. \|remote: Result has 9 objects. \|remote: Deltifying 9 objects. \|remote: 100% (9/9) done \|remote: Unpacking 9 objects \|Total 9, written 9 (delta 8), reused 0 (delta 0) \| 100% (9/9) done The confusion can be avoided in most cases by writing the remote message in one go to prevent interleacing with local messages. The buffer declaration has been moved inside recv_sideband() to avoid extra string copies. Signed-off-by: Nicolas Pitre <nico@cam.org> Signed-off-by: Junio C Hamano <junkio@cox.net>	18 years ago
Junio C Hamano	d47f3db75c	Prepare larger packet buffer for upload-pack protocol. The original side-band support added to the upload-pack protocol used the default 1000-byte packet length. The pkt-line format allows up to 64k, so prepare the receiver for the maximum size, and have the uploader and downloader negotiate if larger packet length is allowed. Signed-off-by: Junio C Hamano <junkio@cox.net>	19 years ago
Junio C Hamano	958c24b1b8	Move sideband server side support into reusable form. The server side support; this is just the very low level, and the caller needs to know which band it wants to send things out. Signed-off-by: Junio C Hamano <junkio@cox.net> (cherry picked from b786552b67878c7780c50def4c069d46dc54efbe commit)	19 years ago
Junio C Hamano	49a52b1d1f	Move sideband client side support into reusable form. This moves the receiver side of the sideband support from fetch-clone.c to sideband.c and its header file, so that archiver protocol can use it. Signed-off-by: Junio C Hamano <junkio@cox.net>	19 years ago