Re: Local cache for git objects

From: Bartosz Gęza <bartoszgeza@gmail.com>
Date: May 17, 2012, 21:11 UTC
Message-ID: <CALnNMuFtp0CoMkiP0W+6bOmd4Y6JD2b5HZuc3qfAuxiJjTcwEA@mail.gmail.com>
In-Reply-To: <xmqqk40a7cwi.fsf@junio.mtv.corp.google.com>

On Thu, May 17, 2012 at 10:47 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 14 quoted lines

>
> 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?

That would work. It's a good practice for a single project with stable dependencies.

My only concern is that it requires effort from user of the cache to keep the list of tracked remotes up to date. After time user would have to recall how to update the list or bother somebody who remembers. I suppose that in a few months since set up it would only include repositories that take over 5-10 minutes to fetch.