On Mon, May 8, 2017 at 3:49 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Junio C Hamano <gitster@xxxxxxxxx> writes: > >> Christian Couder <christian.couder@xxxxxxxxx> writes: >> >>> This patch series contains 2 patches that have already been sent to >>> the list but have felt through the cracks. It would be nice if they >>> could be considered for v2.13.0. >> >> There is no way for anything new to go to 2.13 without getting >> reviewed and discussed at this point---it simply is way too late. Ok, sorry about resending too late. > I found that this is <20170419093314.4454-1-pclouds@xxxxxxxxx> in > mid April (please do not make readers dig the list archive when you > can). > > I didn't see anybody (not even you, to whom the patch was apparently > addressed) commenting back then on the patch and that was why I > didn't touch it. I've skimmed the change in 1/2 now, and although I > didn't see anything glaringly wrong, it would be good to have a test > if this fixes a reproducible crash. It fixes a memory leak not a crash. And this should not be a big problem as shared index files should not be changed often in the same Git process.