From: mailings at hupie.com (Ferry Huberts)
Subject: [PATCH 1/2] avoid memory leak
Date: Fri, 03 Jun 2011 09:19:30 +0200 [thread overview]
Message-ID: <4DE88B02.1060004@hupie.com> (raw)
In-Reply-To: <1307058054-2552-1-git-send-email-jamie.couture@gmail.com>
On 06/03/2011 01:40 AM, jamie.couture at gmail.com wrote:
>
> free rel when we're done
> ---
> scan-tree.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
>
>
>
> _______________________________________________
> cgit mailing list
> cgit at hjemli.net
> http://hjemli.net/mailman/listinfo/cgit
i see no patches...
--
Ferry Huberts
next prev parent reply other threads:[~2011-06-03 7:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jamie.couture@gmail.com>
2011-06-02 23:40 ` jamie.couture
2011-06-02 23:40 ` [PATCH 2/2] Add feature: obtain repo section from git config jamie.couture
2011-06-03 7:19 ` mailings [this message]
2011-06-03 13:54 [PATCH 1/2] avoid memory leak jamie.couture
2011-06-03 23:21 [PATCH 0/2] Set section via git config jamie.couture
2011-06-03 23:21 ` [PATCH 1/2] avoid memory leak jamie.couture
2011-06-06 16:57 ` larsh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DE88B02.1060004@hupie.com \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).