On Mon, Sep 17, 2018 at 7:31 PM Junio C Hamano <gitster@xxxxxxxxx> wrote: > > Duy Nguyen <pclouds@xxxxxxxxx> writes: > > > But it _is_ available now. If you need it, you write the extension > > out. > > Are you arguing for making it omitted when it is not needed (e.g. > small enough index file)? IOW, did you mean "If you do not need it, > you do not write it out" by the above? Yes I did. > I do not think overhead of writing (or preparing to write) the > extension for a small index file is by definition small enough ;-). Good point. I get annoyed by the "ignoring unknown extension xxx" messages while testing though (not just this extension) and I think it will be the same for other git implementations. But perhaps other implementations just silently drop the extension. Most of the extensions we have added so far (except the ancient 'TREE') are optional and are probably not present 99% of time when a different git impl reads an index created by C Git. This 'EIOE' may be a good test then to see if they follow the "ignore optional extensions" rule since it will always appear in new C Git releases. -- Duy
