Michael Haggerty writes:
>>> ... This scenario doesn't currently occur in the code,
>>> but fix it to prevent things from breaking in a very confusing way in
>>> the future.
>>
>> Hopefully that means "in later patches in this series" ;-)
>
> I don't think that the rest of the series would have
On 04/15/2013 07:38 PM, Junio C Hamano wrote:
> Michael Haggerty writes:
>> [...] But more
>> importantly, this change prevents peel_ref() from returning invalid
>> results in the following scenario:
>>
>> When iterating via the external API, the iteration always includes
>> both packed and loose
Michael Haggerty writes:
> Establish an internal API for iterating over references, which gives
> the callback functions direct access to the ref_entry structure
> describing the reference. (Do not change the iteration API that is
> exposed outside of the module.)
>
> Define a new internal callb
Establish an internal API for iterating over references, which gives
the callback functions direct access to the ref_entry structure
describing the reference. (Do not change the iteration API that is
exposed outside of the module.)
Define a new internal callback signature
int each_ref_entry_f
4 matches
Mail list logo
