From: Jari Aalto <jari.aalto@cante.net>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] splint 3.1.1 - Check C programs for security vulnerabilities
Date: Sun, 26 Aug 2007 15:40:00 -0000 [thread overview]
Message-ID: <mywefggq.fsf@cante.net> (raw)
In-Reply-To: <46D193F0.4090505@aim.com> (idirectscm-CZK690njTpI@public.gmane.org's message of "Sun\, 26 Aug 2007 10\:53\:36 -0400")
idirectscm <idirectscm-CZK690njTpI@public.gmane.org> writes:
>> 3.1.2: I took a look at it and there are some issues that need to be resolved>>
> OK. Splint version 3.1.1-1 already is available via setup. Is
> something missing
> from version 3.1.1-1 that would be added in 3.1.1-2?
*-2 is just ITA (adoption) with refined Cygwin/splint*.README (added
License information, detailed contact addresses etc.)
Jari
next prev parent reply other threads:[~2007-08-26 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 15:36 Jari Aalto
2007-08-14 15:54 ` Mark Harig
2007-08-15 15:55 ` Dr. Volker Zell
2007-08-24 22:05 ` Jari Aalto
2007-08-26 10:08 ` [GTG] " Dr. Volker Zell
2007-08-27 12:26 ` Eric Blake
2007-08-26 14:53 ` idirectscm
2007-08-26 15:40 ` Jari Aalto [this message]
2007-08-27 8:31 ` Dr. Volker Zell
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=mywefggq.fsf@cante.net \
--to=jari.aalto@cante.net \
--cc=cygwin-apps@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).