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

Re: Local cache for git objects

From
Junio C Hamano <gitster@pobox.com>
Date
May 17, 2012, 20:47 UTC
Message-ID
<xmqqk40a7cwi.fsf@junio.mtv.corp.google.com>
In-Reply-To
<CALnNMuE=YQsXK-kiRUntNU_0s7s6ONgBk92dZN4UD0Va+qqF+Q@mail.gmail.com>
Bartosz Gęza <bartoszgeza@gmail.com> writes:
> Reference is read only (?)
> I'd like to set up one global cache repository and forget.
> Later as I fetch any objects they are stored there for fast future access.

Somebody needs to keep the "global cache" up to date, and that has to be somebody who has access to cron(7) on your system, and you will be a good candidate to do so. So as part of the procedure to "set up one global cache repository and forget (about it)", make a bare clone and then set up a scheduled task to periodically "git fetch" from its origin, and then you are pretty much done, no?

Previous: Bartosz GęzaNext: Bartosz Gęza
Message 3 of 4 in “Local cache for git objects”
  1. Bartosz GęzaMay 17, 2012
  2. Bartosz GęzaMay 17, 2012
  3. Junio C HamanoMay 17, 2012
  4. Bartosz GęzaMay 17, 2012

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.