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

Re: Dangling blob after git gc

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Nov 27, 2008, 13:53 UTC
Message-ID
<20081127135342.GX4746@genesis.frugalware.org>
In-Reply-To
<vpqzljlnuwo.fsf@bauges.imag.fr>
On Thu, Nov 27, 2008 at 02:46:47PM +0100, Matthieu Moy <Matthieu.Moy@imag.fr> wrote:
Show 11 quoted lines
> from man git-gc:
> 
>      The optional configuration variable gc.pruneExpire controls
>      how old the unreferenced loose objects have to be before
>      they are pruned. The default is "2 weeks ago".
> 
> Git can hardly know for sure whether a dangling object is actually a
> temporary object used by another instance of git or actually an unused
> object. Older versions of Git required you to explicitely say --prune
> to mean "OK, _I_ am sure, you can prune the objects", newer do it the
> safe way by removing only objects old enough.

So it was a user error, thanks for pointing out the relevant documentation. :)

Previous: Matthieu Moy
Message 3 of 3 in “Dangling blob after git gc”
  1. Miklos VajnaNov 27, 2008
  2. Matthieu MoyNov 27, 2008
  3. Miklos VajnaNov 27, 2008

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.