auto gc: don't write bitmaps for incremental repacks
authorDavid Turner <dturner@twosigma.com>
Wed, 28 Dec 2016 22:45:41 +0000 (17:45 -0500)
committerJunio C Hamano <gitster@pobox.com>
Thu, 29 Dec 2016 21:45:35 +0000 (13:45 -0800)
commitbdf56de896b48d6fe3ad90e92138b5fd6579748d
tree1be4c69a1fa9b5222cd4cd2ba8a1d27626a394b7
parentc3808ca6982b0ad7ee9b87eca9b50b9a24ec08b0
auto gc: don't write bitmaps for incremental repacks

When git gc --auto does an incremental repack of loose objects, we do
not expect to be able to write a bitmap; it is very likely that
objects in the new pack will have references to objects outside of the
pack.  So we shouldn't try to write a bitmap, because doing so will
likely issue a warning.

This warning was making its way into gc.log.  When the gc.log was
present, future auto gc runs would refuse to run.

Patch by Jeff King.
Bug report, test, and commit message by David Turner.

Signed-off-by: David Turner <dturner@twosigma.com>
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
builtin/gc.c
t/t6500-gc.sh