In the last commit, we refactored some of the tests in t6500 to make
clearer when cruft packs will and won't be generated by `git gc`.
Add the remaining cases not covered by the previous patch into this one,
which enumerates all possible combinations of arguments that will
produce (or not produce) a cruft pack.
This prepares us for a future commit which will change the default value
of `gc.cruftPacks` by ensuring that we understand which invocations do
and do not change as a result.
Signed-off-by: Taylor Blau <me@xxxxxxxxxxxx>
---
t/t6500-gc.sh | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/t/t6500-gc.sh b/t/t6500-gc.sh
index a2f988c5c2..3ba2ae5140 100755
--- a/t/t6500-gc.sh
+++ b/t/t6500-gc.sh
@@ -218,6 +218,7 @@ assert_no_cruft_packs () {
for argv in \
"gc --cruft" \
"-c gc.cruftPacks=true gc" \
+ "-c gc.cruftPacks=false gc --cruft" \
"-c feature.experimental=true gc" \
"-c gc.cruftPacks=true -c feature.experimental=false gc"
do
@@ -243,6 +244,9 @@ do
done
for argv in \
+ "gc" \
+ "-c gc.cruftPacks=false gc" \
+ "-c gc.cruftPacks=true gc --no-cruft" \
"-c feature.expiremental=true -c gc.cruftPacks=false gc" \
"-c feature.experimental=false gc"
do
--
2.40.0.362.gc67ee7c2ff
