Re: What's cooking in git.git (Jun 2020, #05; Thu, 25)

[Junio C Hamano <gitster@pobox.com>]

Carlo Marcelo Arenas Belón <carenas@gmail.com> writes:

> On Thu, Jun 25, 2020 at 06:12:40PM -0700, Junio C Hamano wrote:
>> 
>> * cb/is-descendant-of (2020-06-23) 1 commit
>>   (merged to 'next' on 2020-06-25 at ca0eaddf5e)
>>  + commit-reach: avoid is_descendant_of() shim
>> 
>>  Code clean-up.
>> 
>>  Will merge to 'master'.
>
> apologize for the most likely unnecessary clarification (probably implied
> by the merged comment indicating ca0eaddf5e), but this branch uses both
> rs/pull-leakfix and rs/commit-reach-leakfix, that are currently merged
> earlier into next and also scheduled for master.

Hmph, Does it break if it is merged alone to 'master' without these
other two topics?  I somehow thought I disentangled the topic from
unnecessary dependencies before queuing it, but it is possible that
I misremember...

>> * jk/fast-export-anonym (2020-06-22) 4 commits
>>   (merged to 'next' on 2020-06-22 at b517b2f707)
>>  + fast-export: allow dumping the path mapping
>>  + fast-export: refactor path printing to not rely on stdout
>>  + fast-export: anonymize "master" refname
>>  + fast-export: allow dumping the refname mapping
>> 
>>  The way refnames are anonymized has been updated and a way to help
>>  debugging using the anonymized output hsa been added.
>
> s/hsa/has

Thanks.