Christian Couder writes:
> When parse_chunk() fails it can return -1, for example
> when find_header() doesn't find a patch header.
>
> In this case it's better in apply_patch() to free the
> "struct patch" that we just allocated instead of
> leaking it.
>
> Signed-off-by: Christian Couder
> ---
On Fri, Apr 1, 2016 at 12:56 AM, Junio C Hamano wrote:
> Christian Couder writes:
>
>> On Wed, Mar 16, 2016 at 3:35 PM, Christian Couder
>> wrote:
>>> When parse_chunk() fails it can return -1, for example
>>> when find_header() doesn't find a patch header.
>>>
>>> In this case it's better in ap
Christian Couder writes:
> On Wed, Mar 16, 2016 at 3:35 PM, Christian Couder
> wrote:
>> When parse_chunk() fails it can return -1, for example
>> when find_header() doesn't find a patch header.
>>
>> In this case it's better in apply_patch() to free the
>> "struct patch" that we just allocated
On Wed, Mar 16, 2016 at 3:35 PM, Christian Couder
wrote:
> When parse_chunk() fails it can return -1, for example
> when find_header() doesn't find a patch header.
>
> In this case it's better in apply_patch() to free the
> "struct patch" that we just allocated instead of
> leaking it.
Maybe this
When parse_chunk() fails it can return -1, for example
when find_header() doesn't find a patch header.
In this case it's better in apply_patch() to free the
"struct patch" that we just allocated instead of
leaking it.
Signed-off-by: Christian Couder
---
builtin/apply.c | 4 +++-
1 file changed,
5 matches
Mail list logo