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/t5700-clone-reference.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/t5700-clone-reference.sh')
| -rwxr-xr-x | t/t5700-clone-reference.sh | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/t/t5700-clone-reference.sh b/t/t5700-clone-reference.sh index ab00e8fb6..dd9caad1c 100755 --- a/t/t5700-clone-reference.sh +++ b/t/t5700-clone-reference.sh @@ -22,7 +22,7 @@ echo second > file2 && git add file2 && git commit -m addition && git repack -a -d && -git prune --grace=off' +git prune' cd "$base_dir" @@ -56,7 +56,7 @@ echo third > file3 && git add file3 && git commit -m update && git repack -a -d && -git prune --grace=off' +git prune' cd "$base_dir" |