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@ttaylorr.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
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
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