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

Re: Confused about `git gc`

From
Yakup Akbay <yakbay@ubicom.com>
Date
Jun 9, 2009, 11:18 UTC
Message-ID
<4A2E451B.3080600@ubicom.com>
In-Reply-To
<m3ljo14r61.fsf@localhost.localdomain>
Jakub Narebski wrote:
Show 24 quoted lines
> Yakup Akbay <yakbay@ubicom.com> writes:
>
>   
>> Looks like I didn't quite understand the actual role of `git gc`. I
>> just thought that `git gc` would remove all unreferenced objects
>> during the unpack-pack process. However, I'm not seeing the result
>> what I was expecting from `git gc`.
>>
>> I'm adding an object into the database, which is ignored by git. Then
>> I expect the object to be removed after `git gc`. But, it's still
>> there.
>>     
>
> [...]
>   
>> What am I overlooking?
>>     
>
> You are probably overlooking the safety introduced to "git gc" to make
> it safer against concurrently run git operations, namely the fact that
> it would not remove new loose objects (it would remove loose objects
> only when they are old enough).
>
>   
Hmm, I see.
    git gc --prune=<date>
helped me remove all loose objects.

Thanks, Yakup

Previous: Jakub Narebski
Message 3 of 3 in “Confused about `git gc`”
  1. Yakup AkbayJun 9, 2009
  2. Jakub NarebskiJun 9, 2009
  3. Yakup AkbayJun 9, 2009

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.