diff options
| author | Junio C Hamano <junkio@cox.net> | 2007-01-22 08:29:44 +0300 |
|---|---|---|
| committer | Junio C Hamano <junkio@cox.net> | 2007-01-22 08:29:57 +0300 |
| commit | 026aa93818a536c819a94aae5bbefe1b6251fe0e (patch) | |
| tree | 4c03787020e72a0957972900f10a5905b1661bec /t/t5400-send-pack.sh | |
| parent | 1bb914603a0f151669de2c31671f6c878c5eb79f (diff) | |
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/t5400-send-pack.sh')
| -rwxr-xr-x | t/t5400-send-pack.sh | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/t/t5400-send-pack.sh b/t/t5400-send-pack.sh index 2a55d5ae32..2c151912a3 100755 --- a/t/t5400-send-pack.sh +++ b/t/t5400-send-pack.sh @@ -55,13 +55,13 @@ test_expect_success setup ' test_expect_success 'pack the source repository' ' git repack -a -d && - git prune --grace=off + git prune ' test_expect_success 'pack the destination repository' ' cd victim && git repack -a -d && - git prune --grace=off && + git prune && cd .. ' |