All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@kernel.org>
To: Neil Booth <neil@daikokuya.co.uk>
Cc: Derek M Jones <derek@knosof.co.uk>, linux-sparse@vger.kernel.org
Subject: Re: Sparse and the Google Summer of Code 2008
Date: Wed, 12 Mar 2008 13:01:06 -0700	[thread overview]
Message-ID: <47D83682.6070409@kernel.org> (raw)
In-Reply-To: <20080312151937.GA29685@daikokuya.co.uk>

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

Neil Booth wrote:
> Josh Triplett wrote:-
>> To clarify, I wouldn't expect a student project to do everything
>> necessary to complete any of the areas I mentioned.  I wouldn't expect
>> complete handling of contexts, or a complete port of an extensive test
>> suite.
> 
> Of course, the real goal should be not a testsuite port to sparse,
> but a testsuite full stop.  One that works with trivial tweaks for
> any given compiler.  That would be of much more value than a
> "port" to sparse or anything else.

Agreed entirely, and I would happily accept such a project under the Sparse
banner.

- Josh Triplett


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

      reply	other threads:[~2008-03-12 20:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 17:38 Sparse and the Google Summer of Code 2008 Alexey Zaytsev
2008-03-11 18:20 ` Josh Triplett
2008-03-11 19:08   ` James Westby
2008-03-11 22:10   ` Christopher Li
2008-03-12  1:41   ` Derek M Jones
2008-03-12  2:20     ` Alexey Zaytsev
2008-03-12  4:28     ` Josh Triplett
2008-03-12 15:19       ` Neil Booth
2008-03-12 20:01         ` Josh Triplett [this message]

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=47D83682.6070409@kernel.org \
    --to=josh@kernel.org \
    --cc=derek@knosof.co.uk \
    --cc=linux-sparse@vger.kernel.org \
    --cc=neil@daikokuya.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.