Re: [PATCH v2 06/27] update_refs(): Fix constness

2014-03-31 Thread Junio C Hamano
Michael Haggerty writes: > On 03/31/2014 11:40 PM, Junio C Hamano wrote: >> Michael Haggerty writes: >> >>> Since full const correctness is beyond the ability of C's type system, >>> just put the const where it doesn't do any harm. A (struct ref_update >>> **) can be passed to a (struct ref_up

Re: [PATCH v2 06/27] update_refs(): Fix constness

2014-03-31 Thread Michael Haggerty
On 03/31/2014 11:40 PM, Junio C Hamano wrote: > Michael Haggerty writes: > >> Since full const correctness is beyond the ability of C's type system, >> just put the const where it doesn't do any harm. A (struct ref_update >> **) can be passed to a (struct ref_update * const *) argument, but not

Re: [PATCH v2 06/27] update_refs(): Fix constness

2014-03-31 Thread Junio C Hamano
Michael Haggerty writes: > Since full const correctness is beyond the ability of C's type system, > just put the const where it doesn't do any harm. A (struct ref_update > **) can be passed to a (struct ref_update * const *) argument, but not > to a (const struct ref_update **) argument. Sounds