From: Bert Wesarg <bert.wesarg@googlemail.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Michael J Gruber <git@drmicha.warpmail.net>,
Jim Meyering <jim@meyering.net>,
git@vger.kernel.org, Bert Wesarg <bert.wesarg@googlemail.com>
Subject: [PATCH v2] builtin-remote: (get_one_entry): use strbuf
Date: Tue, 23 Jun 2009 00:27:44 +0200 [thread overview]
Message-ID: <1245709664-23611-1-git-send-email-bert.wesarg@googlemail.com> (raw)
In-Reply-To: <20090622213204.GB19364@coredump.intra.peff.net>
Signed-off-by: Bert Wesarg <bert.wesarg@googlemail.com>
---
v2: - remove assigment indirection
- keep old code flow
On Mon, Jun 22, 2009 at 23:32, Jeff King <peff@peff.net> wrote:
> But that is somewhat nit-picking. As long as the const-warning goes
> away, I will be happy enough.
>
Thanks for the review. I have no objections to your comments and have all
incroporated into v2.
Thanks,
Bert
> -Peff
builtin-remote.c | 16 +++++++---------
1 files changed, 7 insertions(+), 9 deletions(-)
diff --git a/builtin-remote.c b/builtin-remote.c
index 658d578..2fb76d3 100644
--- a/builtin-remote.c
+++ b/builtin-remote.c
@@ -1276,15 +1276,14 @@ static int update(int argc, const char **argv)
static int get_one_entry(struct remote *remote, void *priv)
{
struct string_list *list = priv;
+ struct strbuf url_buf = STRBUF_INIT;
const char **url;
int i, url_nr;
- void **utilp;
if (remote->url_nr > 0) {
- utilp = &(string_list_append(remote->name, list)->util);
- *utilp = xmalloc(strlen(remote->url[0])+strlen(" (fetch)")+1);
- strcpy((char *) *utilp, remote->url[0]);
- strcat((char *) *utilp, " (fetch)");
+ strbuf_addf(&url_buf, "%s (fetch)", remote->url[0]);
+ string_list_append(remote->name, list)->util =
+ strbuf_detach(&url_buf, NULL);
} else
string_list_append(remote->name, list)->util = NULL;
if (remote->pushurl_nr) {
@@ -1296,10 +1295,9 @@ static int get_one_entry(struct remote *remote, void *priv)
}
for (i = 0; i < url_nr; i++)
{
- utilp = &(string_list_append(remote->name, list)->util);
- *utilp = xmalloc(strlen(url[i])+strlen(" (push)")+1);
- strcpy((char *) *utilp, url[i]);
- strcat((char *) *utilp, " (push)");
+ strbuf_addf(&url_buf, "%s (push)", url[i]);
+ string_list_append(remote->name, list)->util =
+ strbuf_detach(&url_buf, NULL);
}
return 0;
--
tg: (d4b46b0..) bw/remote-v-use-strbuf (depends on: next)
prev parent reply other threads:[~2009-06-22 22:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 19:46 [PATCH] avoid NULL dereference on failed malloc Jim Meyering
2009-06-15 7:49 ` Michael J Gruber
2009-06-15 20:45 ` [PATCH] builtin-remote: (get_one_entry): use strbuf Bert Wesarg
2009-06-16 7:39 ` Michael J Gruber
2009-06-16 7:56 ` Bert Wesarg
2009-06-16 10:49 ` Michael J Gruber
2009-06-22 8:24 ` Bert Wesarg
2009-06-22 21:32 ` Jeff King
2009-06-22 22:27 ` Bert Wesarg [this message]
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=1245709664-23611-1-git-send-email-bert.wesarg@googlemail.com \
--to=bert.wesarg@googlemail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jim@meyering.net \
--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.
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).