git/list[1] front-page[2] threads[3] people[4] search[5] about
 

"There are too many unreachable loose objects" - why don't we run 'git prune' automatically?

From
Lars Schneider <larsxschneider@gmail.com>
Date
Jun 8, 2017, 12:45 UTC
Message-ID
<9C2F2EA2-0C59-4EA2-8C8E-10228FB82D90@gmail.com>
Hi,

I recently ran into "There are too many unreachable loose objects; run 'git prune' to remove them." after a "Auto packing the repository in background for optimum performance." message.

This was introduced with a087cc9 "git-gc --auto: protect ourselves from accumulated cruft" but I don't understand the commit message really.

Why don't we call 'git prune' automatically? I though Git would prune unreachable objects after 90 days by default anyways. Is the warning about unreachable objects that are not yet 90 days old?

Thanks, Lars

Next: Jeff King
Message 1 of 6 in “"There are too many unreachable loose objects" - why don't we run 'git prune' automatically?”
  1. Lars SchneiderJun 8, 2017
  2. Jeff KingJun 9, 2017
  3. Lars SchneiderJun 9, 2017
  4. Jeff KingJun 10, 2017
  5. Lars SchneiderJun 18, 2017
  6. Jeff KingJun 20, 2017

Read the whole thread, see it on lore, or plain text.

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