Revert "prune: --grace=time"
commit026aa93818a536c819a94aae5bbefe1b6251fe0e
authorJunio C Hamano <junkio@cox.net>
Mon, 22 Jan 2007 05:29:44 +0000 (21 21:29 -0800)
committerJunio C Hamano <junkio@cox.net>
Mon, 22 Jan 2007 05:29:57 +0000 (21 21:29 -0800)
tree4c03787020e72a0957972900f10a5905b1661bec
parent1bb914603a0f151669de2c31671f6c878c5eb79f
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.
Documentation/git-prune.txt
builtin-prune.c
t/t1410-reflog.sh
t/t5400-send-pack.sh
t/t5700-clone-reference.sh
t/t5710-info-alternate.sh