path: root/t
diff options
authorJeff King <>2020-02-14 18:22:22 (GMT)
committerJunio C Hamano <>2020-02-14 18:46:22 (GMT)
commit608d9c93658d6ec2d585748ed45218cc1f404640 (patch)
tree8c6a3a82f5c6e4a4e5b6a74b72b004e8be2c2d33 /t
parent55cb10f9b5cd7216652a5879b792bcd7ac173035 (diff)
rev-list: allow bitmaps when counting objects
The prior commit taught "--count --objects" to work without bitmaps. We should be able to get the same answer much more quickly with bitmaps. Note that we punt on the max_count case here. This perhaps _could_ be made to work if we find all of the boundary commits and treat them as UNINTERESTING, subtracting them (and their reachable objects) from the set we return. That implies an actual commit traversal, but we'd still be faster due to avoiding opening up any trees. Given the complexity and the fact that anyone is unlikely to want this, it makes sense to just fall back to the non-bitmap case for now. Signed-off-by: Jeff King <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 't')
1 files changed, 6 insertions, 0 deletions
diff --git a/t/ b/t/
index 6640329..7ba7d29 100755
--- a/t/
+++ b/t/
@@ -74,6 +74,12 @@ rev_list_tests() {
test_cmp expect actual
+ test_expect_success "counting objects via bitmap ($state)" '
+ git rev-list --count --objects HEAD >expect &&
+ git rev-list --use-bitmap-index --count --objects HEAD >actual &&
+ test_cmp expect actual
+ '
test_expect_success "enumerate --objects ($state)" '
git rev-list --objects --use-bitmap-index HEAD >tmp &&
cut -d" " -f1 <tmp >tmp2 &&