From: Derrick Stolee <stolee@gmail.com>
Date: Tue, 21 Aug 2018 14:44:03 GMT
Subject: Re: [PATCH 0/9] multi-pack-index cleanups
Message-ID: <03fd9f73-417c-5afc-a276-d2194eb17668@gmail.com>
In-Reply-To: <CACsJy8CKnXVJYkKM_W=N=Vq-TVXf+YCqZP_uP7B-dN_6xddB=g@mail.gmail.com>

On 8/21/2018 10:34 AM, Duy Nguyen wrote:
> On Mon, Aug 20, 2018 at 6:53 PM Derrick Stolee <dstolee@microsoft.com> wrote:
>> To better understand the implications of the multi-pack-index with
>> other scenarios, I ran the test suite after adding a step to 'git repack'
>> to write a multi-pack-index, and to default core.multiPackIndex to 'true'.
>> This commit is available as [1].
>>
>> ...
>>
>> [1] https://github.com/derrickstolee/git/commit/098dd1d515b592fb165a276241d7d68d1cde0036
>>      DO-NOT-MERGE: compute multi-pack-index on repack.
> It should be able to _merge_ this patch, but only activate it when
> some test environment variable is set. On Travis x86 we run the test
> suite twice, once normal, and once with special features activated
> (see "if test "$jobname" = "linux-gcc"" in ci/run-build-and-tests.sh).
> I don't think midx is incompatible with any of those features, so we
> could activate and run the whole test suite with it too.

Interesting. I'll look into this. A similar approach may work for the 
commit-graph.

Thanks,

-Stolee