From: Miklos Vajna <vmiklos@frugalware.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH 0/3] builtin-branch: use strbuf
Date: Mon, 17 Nov 2008 21:48:34 +0100 [thread overview]
Message-ID: <cover.1226954771.git.vmiklos@frugalware.org> (raw)
These 3 patches do what's in the subject: use the strbuf API instead of
snprintf() / sprintf().
The current risk of writing unallocated memory is low, I think, but
still, the return value of these functions were not checked at several
places.
Miklos Vajna (3):
builtin-branch: use strbuf in delete_branches()
builtin-branch: use strbuf in fill_tracking_info()
builtin-branch: use strbuf in rename_branch()
builtin-branch.c | 65 +++++++++++++++++++++++++++--------------------------
1 files changed, 33 insertions(+), 32 deletions(-)
next reply other threads:[~2008-11-17 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 20:48 Miklos Vajna [this message]
2008-11-17 20:48 ` [PATCH 1/3] builtin-branch: use strbuf in delete_branches() Miklos Vajna
2008-11-17 20:48 ` [PATCH 2/3] builtin-branch: use strbuf in fill_tracking_info() Miklos Vajna
2008-11-17 20:48 ` [PATCH 3/3] builtin-branch: use strbuf in rename_branch() Miklos Vajna
2008-11-18 23:57 ` Junio C Hamano
2008-11-19 1:11 ` Johannes Schindelin
2008-11-19 19:48 ` Lars Hjemli
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=cover.1226954771.git.vmiklos@frugalware.org \
--to=vmiklos@frugalware.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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