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

From: Jakub Narebski <jnareb@gmail.com>
Date: Mar 12, 2008, 18:35 UTC
Message-ID: <m3prtzyens.fsf@localhost.localdomain>
In-Reply-To: <47D8193B.901@nrlssc.navy.mil>

Brandon Casey <casey@nrlssc.navy.mil> writes:

> Is 'git-gc --prune' still useful to end users when those in-the-know can use
> git-prune when they really want all loose unreferenced objects to be removed?

It is one command less to remember (just like with "git tag --verify"
and "git verify-tag"), so I'm all for "git gc --prune" to remain.

> Also, what about clones created with --shared or --reference? Should there be
> a way to disable this functionality? gc.pruneExpire never

That would be nice.

-- 
Jakub Narebski
Poland
ShadeHawk on #git

$ 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.