On Tue, 7 Aug 2018 at 16:36, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Jakub Narebski <jnareb@xxxxxxxxx> writes: >> Junio C Hamano <gitster@xxxxxxxxx> writes: >> >>> * ds/commit-graph-with-grafts (2018-07-19) 8 commits >>> (merged to 'next' on 2018-08-02 at 0ee624e329) >>> ... >>> Will merge to 'master'. >> >> Derrick wrote that he will be sending v2 of this patch series in a few >> weeks, among others to make it use commit-graph feature if replace >> objects are present but not used (as some git hosting services do, see >> core.useReplaceRefs below). > > Ah, thanks for stopping me (albeit a bit too late-ish, but reverting > that merge is easy enough). Do you have a handy reference to stop > me from making the same mistake on this topic later? https://public-inbox.org/git/a3640919-95cf-cca4-d552-4715a031dd7f@xxxxxxxxx/ DS> Since this series now has two dependencies (including Stefan's ref-store DS> fix that I had included in my v1), I'll let those topics settle DS> before I send a new v2. DS> DS> If there are more comments about how I'm handling these cases, then DS> please jump in and tell me. I'll revisit this topic in a few weeks. >> Also, the test for interaction of commit-graph with the grafts file >> feature does not actually test grafts, but replace objects. https://public-inbox.org/git/86bmap7l7a.fsf@xxxxxxxxx/ >>> * jk/core-use-replace-refs (2018-07-18) 3 commits >>> (merged to 'next' on 2018-08-02 at 90fb6b1056) >>> + add core.usereplacerefs config option >>> + check_replace_refs: rename to read_replace_refs >>> + check_replace_refs: fix outdated comment >>> >>> A new configuration variable core.usereplacerefs has been added, >>> primarily to help server installations that want to ignore the >>> replace mechanism altogether. >>> >>> Will merge to 'master'. [...] -- Jakub Narębski
