Re: [PATCH v3 0/6] Create commit-graph file format v2
- From
Derrick Stolee <stolee@gmail.com>
- Date
- May 6, 2019, 13:47 UTC
- Message-ID
- <c827ccb9-4278-0630-ac38-6cf597437678@gmail.com>
- In-Reply-To
- <CAP8UFD2tnkNfgjm=H__=YPG-+BuOHwHs9=OoXnL9wnj_eOtbQg@mail.gmail.com>
On 5/6/2019 4:27 AM, Christian Couder wrote:
Show 12 quoted lines
> On Fri, May 3, 2019 at 3:44 PM Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote: >> 1) We can stat() the "commit-graphs" directory to see if there's any >> new/deleted ones (dir mtime changed), similar to what we do for the >> untracked cache, and can (but I don't think we do...) do for packs/* >> and objects/??/. >> >> As opposed to ".git/objects/info" itself which e.g. has the "packs", >> "alternates" etc. files (can still do it, but more false positives) > > About incremental commit-graph files and alternates, I wonder if they > could work well together. The main use case would be for servers that > use a common repo for all the forks.
We use a "shared object cache" in VFS for Git, implemented as an alternate, so all enlistments share prefetch packs, multi-pack-indexes, and commit-graph files. This is something we are very focused on.
Thanks, -Stolee