From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
Felipe Contreras <felipe.contreras@gmail.com>
Subject: [PATCH 2/4] transport-helper: trivial style cleanup
Date: Wed, 8 May 2013 20:16:56 -0500 [thread overview]
Message-ID: <1368062218-22440-3-git-send-email-felipe.contreras@gmail.com> (raw)
In-Reply-To: <1368062218-22440-1-git-send-email-felipe.contreras@gmail.com>
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
---
transport-helper.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/transport-helper.c b/transport-helper.c
index 835815f..522d791 100644
--- a/transport-helper.c
+++ b/transport-helper.c
@@ -214,9 +214,8 @@ static struct child_process *get_helper(struct transport *transport)
int i;
data->refspec_nr = refspec_nr;
data->refspecs = parse_fetch_refspec(refspec_nr, refspecs);
- for (i = 0; i < refspec_nr; i++) {
+ for (i = 0; i < refspec_nr; i++)
free((char *)refspecs[i]);
- }
free(refspecs);
}
strbuf_release(&buf);
--
1.8.3.rc1.553.gac13664
next prev parent reply other threads:[~2013-05-09 1:18 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 1:16 [PATCH 0/4] trivial patches Felipe Contreras
2013-05-09 1:16 ` [PATCH 1/4] documentation: trivial style cleanups Felipe Contreras
2013-05-09 23:09 ` Junio C Hamano
2013-05-09 1:16 ` Felipe Contreras [this message]
2013-05-09 23:03 ` [PATCH 2/4] transport-helper: trivial style cleanup Junio C Hamano
2013-05-09 1:16 ` [PATCH 3/4] {fast-export,transport-helper}: style cleanups Felipe Contreras
2013-05-09 8:46 ` John Szakmeister
2013-05-09 8:50 ` Felipe Contreras
2013-05-09 9:30 ` John Szakmeister
2013-05-09 10:18 ` Felipe Contreras
2013-05-09 10:24 ` Ramkumar Ramachandra
2013-05-09 11:06 ` Felipe Contreras
2013-05-09 18:38 ` Junio C Hamano
2013-05-09 19:23 ` Felipe Contreras
2013-05-09 23:09 ` Junio C Hamano
2013-05-09 23:12 ` Felipe Contreras
2013-05-16 9:23 ` Felipe Contreras
2013-05-16 16:19 ` Junio C Hamano
2013-05-16 16:32 ` Felipe Contreras
2013-05-16 16:49 ` Junio C Hamano
2013-05-16 17:02 ` Felipe Contreras
2013-05-16 18:10 ` Junio C Hamano
2013-05-16 18:34 ` Ramkumar Ramachandra
2013-05-16 23:58 ` Felipe Contreras
2013-05-16 23:54 ` Felipe Contreras
2013-05-17 0:24 ` Felipe Contreras
2013-05-17 6:04 ` Ramkumar Ramachandra
2013-05-17 6:09 ` Felipe Contreras
2013-05-17 16:22 ` Junio C Hamano
2013-05-17 16:35 ` Felipe Contreras
2013-05-17 16:56 ` Matthieu Moy
2013-05-17 17:02 ` Felipe Contreras
2013-05-17 17:14 ` Matthieu Moy
2013-05-17 17:18 ` Felipe Contreras
2013-05-09 1:16 ` [PATCH 4/4] fast-export: trivial cleanup Felipe Contreras
2013-05-09 8:52 ` John Szakmeister
2013-05-09 8:53 ` Felipe Contreras
2013-05-09 9:04 ` John Szakmeister
2013-05-09 18:52 ` Junio C Hamano
2013-05-16 9:18 ` Felipe Contreras
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1368062218-22440-3-git-send-email-felipe.contreras@gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).