Re: ds/multi-pack-index (was Re: What's cooking in git.git (Jul 2018, #03; Wed, 25))

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 1, 2018, 22:13 UTC
Message-ID: <xmqqo9el68he.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <f17a6d57-e6cb-9efa-d648-cd4f298dc47f@gmail.com>

Derrick Stolee <stolee@gmail.com> writes:

Show 7 quoted lines

> On 7/25/2018 6:13 PM, Junio C Hamano wrote:
>> * ds/multi-pack-index (2018-07-20) 23 commits
>> ...
>>   Ready to move to 'next', with some known issues to be followed up?
>>   cf. <xmqqefg8uplg.fsf@gitster-ct.c.googlers.com>
> I'm not sure if there is anything actionable for me to do in response
> to this message.

As I said elsewhere, "cf. <msg>" list does not attempt to be a complete enumeration of things to be fixed. It is a (sub)set of pointers into list archive to help me in integration cycles to decide if I can comfortably merge each topic to 'next' (or update "What's cooking" to mark the topic as "Will merge"). FWIW, that particular message is not even an objection ;-) It was telling the future-me "hey, I looked at this series and found nothing wrong in it, so no need to read them again to refresh your memory".

The other one is a good reminder, again, given primarily to future-me, that the topic is known to be imperfect and the discussion seemed to favor moving "with some known issues to be followed up", so I should not waste time re-reading and poke the same holes.