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

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 12, 2008, 20:35 UTC
Message-ID: <7vejaf65q0.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <47D83C53.7000602@nrlssc.navy.mil>

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

> I am not suggesting that git-gc stop parsing --prune and instead start
> erroring out on it. If it is ok to change the behavior of git-gc, it
> seems like it is ok to change the behavior of 'git-gc --prune' in the
> same way, especially if the change makes it less destructive.

Yeah, gc.pruneexpire does sound like it applies to both implicit ones and explicit ones, doesn't it? I think your suggestion makes sense.

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