From: Elijah Newren <newren@gmail.com>
Date: Tue, 18 Mar 2025 06:43:47 GMT
Subject: Re: [PATCH v4 11/13] pack-bitmap.c: keep track of each layer's type bitmaps
Message-ID: <CABPp-BE3dfXa8xda2M2zMH_Qhf_RPggBpC=tx8qaDpCmbr9hWA@mail.gmail.com>
In-Reply-To: <a29f4ee60d519318d36a8d3c812b4bad039b891e.1741983492.git.me@ttaylorr.com>

On Fri, Mar 14, 2025 at 1:18 PM Taylor Blau <me@ttaylorr.com> wrote:
>
> Prepare for reading the type-level bitmaps from previous bitmap layers
> by maintaining an array for each type, where each element in that type's
> array corresponds to one layer's bitmap for that type.
>
> These fields will be used in a later commit to instantiate the 'struct
> ewah_or_iterator' for each type.
>

All I spotted was some possible wording fixups...

> +        *
> +        * When either associated either with a non-incremental MIDX, or
> +        * a single packfile, these arrays each contain a single
> +        * element.
> +        */

Drop the first "either", and the first comma?