Re: [PATCH] gc: call "prune --expire 2.weeks.ago"

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Mar 12, 2008, 23:30 UTC
Message-ID: <alpine.LSU.1.00.0803130028550.1656@racer.site>
In-Reply-To: <7vtzjb34y0.fsf@gitster.siamese.dyndns.org>

Hi,

On Wed, 12 Mar 2008, Junio C Hamano wrote:

> In any case, after 90 days, my reading of the code is that these loose 
> ones become unreachable, and when we look at their timestamps, we notice 
> that they are already more than 2 weeks old, and they will immediately 
> be removed.

Yes.

In any case, most likely these objects would have been packed anyway during that period, so they would have been pruned by the repack called by git-gc.

My patch really, really is about _unreferenced_ loose objects, i.e. something you get by multiple "git add"s without commits. And by merge conflicts.

IOW by objects that were never referenced by commit objects.

Ciao, Dscho

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.