Commits


work around spurious ACK responses from git servers in got-fetch-pack The Git server can apparently send duplicate ACK responses even though we do not enable the multi_ack capability. According to the Git protocol docs the server should only send ACKs after receiving 'done' from the client if multi_ack has been enabled. However, a duplicate ACK response can be triggered by running 'got fetch -a' in our fetch_update_tag test. This resulted in the following error: got-fetch-pack: unknown side-band received from server got: bad packet received


use size_t for loop indices to avoid signedness warnings; by emaste@freebsd Same change as 16aeacf7088d, for subdirectories other than lib/


indentation fixes


Stop including <sys/syslimits.h> directly. POSIX says the limits defined there are available from <limits.h>, which almost all affected source files already included anyway. ok millert stsp


zap trailing tabs


do not rely on <zlib.h> to pull in <unistd.h> ok stsp


Fix missing block grouping. ok tracey stsp


represent packfile hash as byte array in the privsep layer, not as object ID


compute pack file's checksum during download and check it in got-fetch-pack Compared to the previous version committed in 520a0c97 this code should compute the checksum correctly for any amount of pack file data bytes read from the socket at a time.


revert 520a0c97f8081e4531fc9c88cda705a92afbddaf for now due to possible bug


compute pack file's checksum during download and check it in got-fetch-pack


move functions from privsep.c to the helpers which use them where possible


add support for fetching arbitrary references to 'got clone' and 'got fetch'


remove GOT_FETCH_DEBUG and toggle fetch debug output with -v option instead


close fetchfd when we're done in got-fetch-pack