From: Junio C Hamano Date: Tue, 04 Oct 2016 04:01:27 GMT Subject: Re: What's cooking in git.git (Oct 2016, #01; Mon, 3) Message-ID: In-Reply-To: <20161004005247.sgeqgw3accn3whgi@sigill.intra.peff.net> Jeff King writes: >> * lt/abbrev-auto (2016-10-03) 3 commits > > I kind of expected this one to cook in next for a bit while people > decided whether the larger hashes were irritating or not. Despite > working on the implementation, I'm on the fence myself. > > I'd kind of hoped people would play with core.disambiguate and the hints > and see if they still actually wanted to bump the default abbrev (and > how aggressively to do so; if core.disambiguate means most of the > ambiguity is just between commits, that cuts the number of > collision-interesting objects by an order of magnitude). Sure. Let's keep them cooking. >> * jk/pack-objects-optim-mru (2016-08-11) 4 commits >> (merged to 'next' on 2016-09-21 at 97b919bdbd) >> + pack-objects: use mru list when iterating over packs >> + pack-objects: break delta cycles before delta-search phase >> + sha1_file: make packed_object_info public >> + provide an initializer for "struct object_info" >> >> Originally merged to 'next' on 2016-08-11 >> >> "git pack-objects" in a repository with many packfiles used to >> spend a lot of time looking for/at objects in them; the accesses to >> the packfiles are now optimized by checking the most-recently-used >> packfile first. >> >> Will hold to see if people scream. > > This has been in next for 6 weeks. Is it time to consider graduating it? Perhaps.