![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
| author | Junio C Hamano <junkio@cox.net> | |
| Mon, 22 Jan 2007 05:29:44 +0000 (21:29 -0800) | ||
| committer | Junio C Hamano <junkio@cox.net> | |
| Mon, 22 Jan 2007 05:29:57 +0000 (21:29 -0800) | ||
| commit | 026aa93818a536c819a94aae5bbefe1b6251fe0e | |
| tree | 4c03787020e72a0957972900f10a5905b1661bec | tree | snapshot |
| parent | 1bb914603a0f151669de2c31671f6c878c5eb79f | commit | 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.
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.