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

Re: Dealing with many many git repos in a /home directory

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Feb 4, 2010, 15:00 UTC
Message-ID
<46a038f91002040700x623a686ek4bc35d20f5d9cb86@mail.gmail.com>
In-Reply-To
<9b18b3111002040029x1c7de0afw4a5ef883588f7a18@mail.gmail.com>
On Thu, Feb 4, 2010 at 3:29 AM, demerphq <demerphq@gmail.com> wrote:
> This is starting to take a lot of space.
What I used to do was to
 - have a "canonical" local bare repo for each major project, fetching
and repacking nightly
 - a script that "injects" an "alternates" entry to matching user
repos -- logic to look at a repo and decide which alternate to hook it
to is left to the reader.
 - optional: automating repacks on users repos

As users repack, their "local" packs will only have the objects that are not shared with the canonical repos. With Moodle repos, this was a 200MB savings per repo.

And the kernel keeps one set of packfiles in buffers, so everyone gets much faster gitk / gitlog / blame...

m
-- 
 martin.langhoff@gmail.com
 martin@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
Previous: SergioNext: Andreas Schwab
Message 4 of 6 in “Dealing with many many git repos in a /home directory”
  1. demerphqFeb 4, 2010
  2. Alex RiesenFeb 4, 2010
  3. SergioFeb 4, 2010
  4. Martin LanghoffFeb 4, 2010
  5. Andreas SchwabFeb 4, 2010
  6. Nicolas PitreFeb 4, 2010

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.