path: root/t/helper/test-tool.c
diff options
authorTaylor Blau <>2021-04-01 01:32:11 (GMT)
committerJunio C Hamano <>2021-04-01 06:14:03 (GMT)
commit483fa7f42d9e7723154aa1baa6e1576cf51cc64b (patch)
tree589b0a6fe367a6e9ece7e5b4c49860b7e5bff835 /t/helper/test-tool.c
parentdff5e49e51bfddbbeb5ed1f07031ccbd0bc216dc (diff)
t/helper/test-bitmap.c: initial commit
Add a new 'bitmap' test-tool which can be used to list the commits that have received bitmaps. In theory, a determined tester could run 'git rev-list --test-bitmap <commit>' to check if '<commit>' received a bitmap or not, since '--test-bitmap' exits with a non-zero code when it can't find the requested commit. But this is a dubious behavior to rely on, since arguably 'git rev-list' could continue its object walk outside of which commits are covered by bitmaps. This will be used to test the behavior of 'pack.preferBitmapTips', which will be added in the following patch. Signed-off-by: Taylor Blau <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 't/helper/test-tool.c')
1 files changed, 1 insertions, 0 deletions
diff --git a/t/helper/test-tool.c b/t/helper/test-tool.c
index f97cd9f..a48bd44 100644
--- a/t/helper/test-tool.c
+++ b/t/helper/test-tool.c
@@ -15,6 +15,7 @@ struct test_cmd {
static struct test_cmd cmds[] = {
{ "advise", cmd__advise_if_enabled },
+ { "bitmap", cmd__bitmap },
{ "bloom", cmd__bloom },
{ "chmtime", cmd__chmtime },
{ "config", cmd__config },