So I reviewed and examined this series and run into some problems. How do we view an empty reflog, i.e. an empty file at logs/refs/heads/master? I was told this is not a valid state for a reflog. However even the test suite sometimes produces an empty reflog files. Below there is a patch, which highlights the empty reflog when running t1301.sh verbosely.
--- t/t1301-shared-repo.sh | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/t/t1301-shared-repo.sh b/t/t1301-shared-repo.sh index de42d21..6a35fc0 100755 --- a/t/t1301-shared-repo.sh +++ b/t/t1301-shared-repo.sh @@ -113,7 +113,9 @@ done test_expect_success POSIXPERM 'git reflog expire honors core.sharedRepository' ' git config core.sharedRepository group && - git reflog expire --all && + git reflog master && + git reflog expire --all --verbose && + git reflog master && actual="$(ls -l .git/logs/refs/heads/master)" && case "$actual" in -rw-rw-*) -- 2.2.0 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
