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

Re: gc.linkedobjectdir discussion

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 24, 2015, 22:26 UTC
Message-ID
<xmqqsidvosjj.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CAFwrLX7AVbhbP-Ha3Vag+7o5a-8fSaQxxx+z0DRurdzY-pBwkQ@mail.gmail.com>
Will Entriken <fulldecent@gmail.com> writes:
> USAGE - CACHE HIT:
> During another pull or clone on a different working directory, git
> will find the required object in LINKEDOBJECTDIR and hard link into
> the active repo's object store.

What happens when the necessary objects are in a packfile, mixed with other objects that this repository does not need but may be necessary for other repositories?

> USAGE - DELETING:
> Whenever deleting an object, git will stat the file to see to see if
> its link count is 2, if so, both copies are deleted.

This is totally unworkable if you ever pack your repository. And packing loose objects is a lot more efficient way to reduce your disk footprint than sharing the object store among a handful of repositories.

Previous: Will Entriken
Message 2 of 2 in “gc.linkedobjectdir discussion”
  1. Will EntrikenFeb 24, 2015
  2. Junio C HamanoFeb 24, 2015

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.