From: Martin Langhoff <martin.langhoff@gmail.com>
To: demerphq <demerphq@gmail.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: Dealing with many many git repos in a /home directory
Date: Thu, 4 Feb 2010 10:00:38 -0500 [thread overview]
Message-ID: <46a038f91002040700x623a686ek4bc35d20f5d9cb86@mail.gmail.com> (raw)
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
next prev parent reply other threads:[~2010-02-04 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 8:29 Dealing with many many git repos in a /home directory demerphq
2010-02-04 9:57 ` Alex Riesen
2010-02-04 15:20 ` Sergio
2010-02-04 15:00 ` Martin Langhoff [this message]
2010-02-04 15:32 ` Andreas Schwab
2010-02-04 17:35 ` Nicolas Pitre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46a038f91002040700x623a686ek4bc35d20f5d9cb86@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=demerphq@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).