From: Jeff King <peff@xxxxxxxx> Using free() on a refspec was always leaky, as its string fields also need freed. But it became more so when ad00f128d (clone: respect configured fetch respecs during initial fetch, 2016-03-30) taught clone to create a list of refspecs, each of which need to be freed. [sg: adjusted the function parameters.] Signed-off-by: Jeff King <peff@xxxxxxxx> Signed-off-by: SZEDER Gábor <szeder.dev@xxxxxxxxx> --- builtin/clone.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/builtin/clone.c b/builtin/clone.c index 4144190da..4bf28d7f5 100644 --- a/builtin/clone.c +++ b/builtin/clone.c @@ -1120,6 +1120,6 @@ int cmd_clone(int argc, const char **argv, const char *prefix) strbuf_release(&value); junk_mode = JUNK_LEAVE_ALL; - free(refspec); + free_refspec(remote->fetch_refspec_nr + 1, remote->fetch); return err; } -- 2.13.0.35.g14b6294b1