On Mon, Aug 07, 2017 at 06:44:16PM -0700, Junio C Hamano wrote:
Having said that, I am a bit curious how you came to this patch.
Was the issue found by code inspection, or did you actually have a
real life use case to raise the core.bigFileThreshold configuration
to a value above 4GB?
Real life use - tracking changes in larger files.
Raising the limit above 4GB suddenly resulted in a broken pack files in the repository and
aborts of various git commands.
Data is still recoverable with all size sanity checks disabled.
Regards,
Martin