Re: What's cooking in git.git (Aug 2018, #01; Thu, 2)

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 7, 2018, 14:36 UTC
Message-ID: <xmqqk1p2mefp.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <86effapi1t.fsf@gmail.com>

Jakub Narebski <jnareb@gmail.com> writes:

Show 11 quoted lines

> Junio C Hamano <gitster@pobox.com> 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?

Show 17 quoted lines

>
> Also, the test for interaction of commit-graph with the grafts file
> feature does not actually test grafts, but replace objects.
>
>> * 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'.
>
> Nice to have features used in the wild merged into core git.

Yes, indeed.