diff options
| author | Junio C Hamano <junkio@cox.net> | 2007-01-21 21:29:44 -0800 |
|---|---|---|
| committer | Junio C Hamano <junkio@cox.net> | 2007-01-21 21:29:57 -0800 |
| commit | 026aa93818a536c819a94aae5bbefe1b6251fe0e (patch) | |
| tree | 4c03787020e72a0957972900f10a5905b1661bec /t/t1410-reflog.sh | |
| parent | 1bb914603a0f151669de2c31671f6c878c5eb79f (diff) | |
| download | git-026aa93818a536c819a94aae5bbefe1b6251fe0e.tar.gz git-026aa93818a536c819a94aae5bbefe1b6251fe0e.tar.xz | |
Revert "prune: --grace=time"
This reverts commit 9b088c4e394df84232cfd37aea78349a495b09c1.
Protecting 'mature' objects does not make it any safer. We should
admit that git-prune is inherently unsafe when run in parallel with
other operations without involving unwarranted locking overhead,
and with the latest git, even rebase and reset would not immediately
create crufts anyway.
Diffstat (limited to 't/t1410-reflog.sh')
| -rwxr-xr-x | t/t1410-reflog.sh | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/t/t1410-reflog.sh b/t/t1410-reflog.sh index 0c435f957..8e8d526ef 100755 --- a/t/t1410-reflog.sh +++ b/t/t1410-reflog.sh @@ -96,7 +96,7 @@ test_expect_success setup ' check_have A B C D E F G H I J K L && - git prune --grace=off && + git prune && check_have A B C D E F G H I J K L && @@ -115,7 +115,7 @@ test_expect_success rewind ' check_have A B C D E F G H I J K L && - git prune --grace=off && + git prune && check_have A B C D E F G H I J K L && @@ -160,7 +160,7 @@ test_expect_success 'reflog expire' ' test_expect_success 'prune and fsck' ' - git prune --grace=off && + git prune && check_fsck && check_have A B C D E H L && |