author | Nicolas Pitre <nico@cam.org> | |
Wed, 12 Nov 2008 18:23:58 +0000 (13:23 -0500) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Wed, 12 Nov 2008 22:55:03 +0000 (14:55 -0800) | ||
commit | a1e4760fcfece8eb9b556f35a04a521fdee3963c | |
tree | 4923753aaa855dedfab330b250856b99cca5cea2 | tree | snapshot |
parent | fa7b3c2f752a10a5dca9989d4a1c4b93ffa7f943 | commit | diff |
Fix pack.packSizeLimit and --max-pack-size handling
If the limit was sufficiently low, having a single object written
could bust the limit (by design), but caused the remaining allowed
size to go negative for subsequent objects, which for an unsigned
variable is a rather huge limit.
Signed-off-by: Nicolas Pitre <nico@cam.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
If the limit was sufficiently low, having a single object written
could bust the limit (by design), but caused the remaining allowed
size to go negative for subsequent objects, which for an unsigned
variable is a rather huge limit.
Signed-off-by: Nicolas Pitre <nico@cam.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
builtin-pack-objects.c | diff | blob | history | |
t/t5300-pack-object.sh | diff | blob | history |