# [PATCH 12/23] transport.c::get_refs_via_curl(): do not leak refs_url

3 messages from 2009-06-05 to 2009-06-06. Participants: Tay Ray Chuan, Jakub Narebski.
Thread: https://gitlist.dev/t/19689

## Tay Ray Chuan, 2009-06-05 16:04

Subject: [PATCH 12/23] transport.c::get_refs_via_curl(): do not leak refs_url
Message-ID: <20090606000451.262b7711.rctay89@gmail.com>
URL: https://gitlist.dev/e/20090606000451.262b7711.rctay89%40gmail.com

```
From:	Mike Hommey <mh@glandium.org>
Subject: [WIP Patch 02/12] Some cleanup in get_refs_via_curl()
Date:	Sun, 18 Jan 2009 09:04:27 +0100

Signed-off-by: Mike Hommey <mh@glandium.org>
Signed-off-by: Tay Ray Chuan <rctay89@gmail.com>
---
 transport.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/transport.c b/transport.c
index efecb65..9edd5aa 100644
--- a/transport.c
+++ b/transport.c
@@ -519,6 +519,7 @@ static struct ref *get_refs_via_curl(struct transport *transport, int for_push)
 		free(ref);
 	}

+	free(refs_url);
 	return refs;
 }

--
1.6.3.1

```

## Jakub Narebski, 2009-06-05 20:46

Subject: Re: [PATCH 12/23] transport.c::get_refs_via_curl(): do not leak refs_url
Message-ID: <m3my8m5ryh.fsf@localhost.localdomain>
URL: https://gitlist.dev/e/m3my8m5ryh.fsf%40localhost.localdomain
In-Reply-To: <20090606000451.262b7711.rctay89@gmail.com>

```
Tay Ray Chuan <rctay89@gmail.com> writes:

> From:	Mike Hommey <mh@glandium.org>
> Subject: [WIP Patch 02/12] Some cleanup in get_refs_via_curl()

So what is the title of this patch? "transport.c::get_refs_via_curl():
do not leak refs_url" or "Some cleanup in get_refs_via_curl()"?

Perhaps it should be "transport.c: Do not leak refs_url in
get_refs_via_curl()"...?

> Date:	Sun, 18 Jan 2009 09:04:27 +0100
> 
> Signed-off-by: Mike Hommey <mh@glandium.org>
> Signed-off-by: Tay Ray Chuan <rctay89@gmail.com>
> ---
>  transport.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/transport.c b/transport.c
> index efecb65..9edd5aa 100644
> --- a/transport.c
> +++ b/transport.c
> @@ -519,6 +519,7 @@ static struct ref *get_refs_via_curl(struct transport *transport, int for_push)
>  		free(ref);
>  	}
> 
> +	free(refs_url);
>  	return refs;
>  }
> 
> --
> 1.6.3.1
> 

-- 
Jakub Narebski
Poland
ShadeHawk on #git

```

## Tay Ray Chuan, 2009-06-06 01:04

Subject: Re: [PATCH 12/23] transport.c::get_refs_via_curl(): do not leak refs_url
Message-ID: <be6fef0d0906051804k4d574d39v37dedf46896cb570@mail.gmail.com>
URL: https://gitlist.dev/e/be6fef0d0906051804k4d574d39v37dedf46896cb570%40mail.gmail.com
In-Reply-To: <m3my8m5ryh.fsf@localhost.localdomain>

```
Hi,

On Sat, Jun 6, 2009 at 4:46 AM, Jakub Narebski<jnareb@gmail.com> wrote:
>> From: Mike Hommey <mh@glandium.org>
>> Subject: [WIP Patch 02/12] Some cleanup in get_refs_via_curl()
>
> So what is the title of this patch? "transport.c::get_refs_via_curl():
> do not leak refs_url" or "Some cleanup in get_refs_via_curl()"?

See my reply to patch #19.

> Perhaps it should be "transport.c: Do not leak refs_url in
> get_refs_via_curl()"...?

I think it's a matter of preference. I'll put them side-by-side to
demonstrate this better:

transport.c: Do not leak refs_url in get_refs_via_curl()
transport.c::get_refs_via_curl(): do not leak refs_url

There isn't any important difference between the two other than form.

-- 
Cheers,
Ray Chuan

```