Re: [PATCH] prune-packed: new option --min-age=N

From: Shawn O. Pearce <spearce@spearce.org>
Date: Jan 18, 2007, 17:51 UTC
Message-ID: <20070118175134.GH15428@spearce.org>
In-Reply-To: <20070118174244.GA14287@moooo.ath.cx>

Matthias Lederhofer <matled@gmx.net> wrote:

> I just remembered people were warning about automatic prune-packed
> (e.g. cron), so this patch does not make much sense anymore.

I think we've resolved it.  There may be some hole we aren't aware
of, but I doubt one exists.  The last hole was packs could be
removed by repack while they were still being brought in during
push or 'fetch -k', but that was fixed with the .keep file.

> Any comments about adding such an option to git prune for unpacked
> objects?  This would allow to run git prune automatically on
> repositories while new objects are created.

An age makes sense on just plain prune. If the loose object was last modified several hours ago and its not being referenced by anything currently, its probably safe to remove.

If you are going to implement this I would suggest making the default age 2 hours and allow the user to configure it from a gc.pruneexpire configuration option, much like gc.reflogexpire.

-- 
Shawn.