From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: Christopher Li <sparse@chrisli.org>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: SSSA and some C pointer manipulation.
Date: Sun, 20 Aug 2017 16:45:33 +0200 [thread overview]
Message-ID: <CAExDi1T5a_exYvJUT5G11URvETEv7TKYcrEj5CJFhBrH+_ZXGw@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxcez1YcYwY9SMW4mNpT-o3cm0C8u==QJFzfPvjehiBQ2A@mail.gmail.com>
On Sun, Aug 20, 2017 at 2:33 AM, Dibyendu Majumdar
<mobile@majumdar.org.uk> wrote:
>
> I think you are raising a deeply philosophical issue.
It was only a pragmatic issue.
> I firmly believe
> all tests are good and needed, and take the pragmatic view that I will
> use whatever tests I can lay my hands on.
Of course.
> Sure we want unit tests as
> these help debug problems. But these need to be written by whoever is
> developing a feature or enhancement. Perhaps Sparse should adopt the
> contribution policy that no changes should be accepted without
> accompanying unit tests.
Patches for the test suite are certainly most welcome.
-- Luc
next prev parent reply other threads:[~2017-08-20 14:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 2:46 SSSA and some C pointer manipulation Christopher Li
2017-08-19 9:46 ` Dibyendu Majumdar
2017-08-19 10:56 ` Christopher Li
2017-08-19 11:57 ` Dibyendu Majumdar
2017-08-19 12:39 ` Christopher Li
2017-08-20 0:08 ` Luc Van Oostenryck
2017-08-20 0:33 ` Dibyendu Majumdar
2017-08-20 14:45 ` Luc Van Oostenryck [this message]
2017-08-20 16:18 ` Luc Van Oostenryck
2017-08-21 3:29 ` Christopher Li
2017-08-21 3:41 ` Christopher Li
2017-08-23 1:03 ` Luc Van Oostenryck
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=CAExDi1T5a_exYvJUT5G11URvETEv7TKYcrEj5CJFhBrH+_ZXGw@mail.gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=mobile@majumdar.org.uk \
--cc=sparse@chrisli.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).