Duy Nguyen <pclo...@gmail.com> writes: > In that case we can just check config once in read_index_from and > destroy UNTR extension. Or the middle ground, we check config once in > that place, make a note in struct index_state, and make invalidate_* > check that note instead of config file. The middle ground has an > advantage over destroying UNTR: (probably) many operations will touch > index but do not add or remove entries.
Or we can even teach read_index_from() to skip reading the extension without even parsing when the configuration tells it that the feature is force-disabled. It can also add an empty one when the configuration tells it that the feature is force-enabled and there is no UNTR extension yet. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
