Patrick Steinhardt 223e7e43ef patch_parse: reject patches with multiple old/new paths ...

It's currently possible to have patches with multiple old path name
headers. As we didn't check for this case, this resulted in a memory
leak when overwriting the old old path with the new old path because we
simply discarded the old pointer.

Instead of fixing this by free'ing the old pointer, we should reject
such patches altogether. It doesn't make any sense for the "---" or
"+++" markers to occur multiple times within a patch n the first place.
This also implicitly fixes the memory leak.

2019-10-19 17:02:53 +02:00

..

parse.c

patch_parse: reject patches with multiple old/new paths

2019-10-19 17:02:53 +02:00

patch_common.h

patch_parse: reject patches with multiple old/new paths

2019-10-19 17:02:53 +02:00

print.c

Convert usage of git_buf_free to new git_buf_dispose

2018-06-10 19:34:37 +02:00