git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Koch, Rick (Subcontractor)" <Rick.Koch@tbe.com>
To: "'git@vger.kernel.org'" <git@vger.kernel.org>
Subject: CPPCheck found 24 high risk bugs in Git v.1.8.3.4
Date: Mon, 19 Aug 2013 12:09:34 -0500	[thread overview]
Message-ID: <85C8141E5DAD94428A121F706995A31F010F116FDAD3@MX1.net.tbe.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 423 bytes --]

I'm directing to this e-mail, as it seems to be the approved forum for posting Git bugs. We ran CPPCheck against Git v.1.8.3.4 and found 24 high risk bugs.  Please see the attachment xlsx. 

Is there a method to post to the Git community to allow the community to review and debunk as faults positive or develop patches to fix lists code files?

v/r

Roderick (Rick) Koch
Information Assurance
Rick.Koch@tbe.com


[-- Attachment #2: CPPCheck_on_Git.v1.8.3.4.xlsx --]
[-- Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet, Size: 10741 bytes --]

             reply	other threads:[~2013-08-19 17:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19 17:09 Koch, Rick (Subcontractor) [this message]
2013-08-19 20:03 ` CPPCheck found 24 high risk bugs in Git v.1.8.3.4 Philip Oakley
2013-08-19 20:40   ` Jeff King
2013-08-19 20:46     ` Junio C Hamano
2013-08-19 20:52       ` Johan Herland
     [not found]   ` <85C8141E5DAD94428A121F706995A31F010F116FDADE@MX1.net.tbe.com>
2013-08-19 21:46     ` Philip Oakley
2013-08-23 19:51       ` CPPCheck found 24 high risk bugs in Git v.1.8.3.4 (fetch.c L588) Philip Oakley
2013-08-19 22:55   ` CPPCheck found 24 high risk bugs in Git v.1.8.3.4 Philip Oakley
2013-08-19 23:15     ` Erik Faye-Lund
2013-08-20 14:33       ` Jeff King
2013-08-20 18:44       ` Andreas Schwab
2013-08-20 20:34         ` René Scharfe
2013-08-20 22:28           ` Erik Faye-Lund
2013-08-20 22:26         ` Erik Faye-Lund
2013-08-20 23:01           ` Andreas Schwab
2013-08-20 23:45             ` Junio C Hamano
2013-08-21  0:01             ` Erik Faye-Lund
2013-08-19 21:36 ` Stefan Beller

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=85C8141E5DAD94428A121F706995A31F010F116FDAD3@MX1.net.tbe.com \
    --to=rick.koch@tbe.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. 
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).