From: Morten Welinder <mwelinder@gmail.com>
To: GIT Mailing List <git@vger.kernel.org>
Subject: diff_tree_stdin
Date: Tue, 11 Oct 2005 21:46:38 -0400 [thread overview]
Message-ID: <118833cc0510111846q42c5d7e5j162bdacd49dfebbc@mail.gmail.com> (raw)
It looks like diff_tree_stdin can overrun the this_header buffer. Since the
line length is already calculated, a check would be cheap.
Morten
next reply other threads:[~2005-10-12 21:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 1:46 Morten Welinder [this message]
2005-10-13 7:11 ` diff_tree_stdin Junio C Hamano
2005-10-13 15:01 ` diff_tree_stdin Morten Welinder
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=118833cc0510111846q42c5d7e5j162bdacd49dfebbc@mail.gmail.com \
--to=mwelinder@gmail.com \
--cc=git@vger.kernel.org \
/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).