git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Google Summer of Code 2007

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 27, 2007, 20:47 UTC
Message-ID
<Pine.LNX.4.63.0702272144580.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<20070225075917.GC1676@spearce.org>
Hi,
On Sun, 25 Feb 2007, Shawn O. Pearce wrote:
> Thoughts?
The projects I would suggest are
1. Make more complete tests.
2. Use sparse to fix errors revealed by static code analysis.
3. Make more things builtin.

Regarding 2: this would be more of a sparse project IMHO. It could mean that sparse actually learns about fixing trivial bugs. (You need to inspect the result, but verifying is faster than writing.)

Ciao, Dscho

Previous: Shawn O. PearceNext: Andy Parkins
Message 2 of 13 in “Google Summer of Code 2007”
  1. Shawn O. PearceFeb 25, 2007
  2. Johannes SchindelinFeb 27, 2007
  3. Andy ParkinsFeb 28, 2007
  4. Matthieu MoyFeb 28, 2007
  5. Johannes SchindelinMar 2, 2007
  6. Raimund BauerFeb 28, 2007
  7. Brian GernhardtFeb 28, 2007
  8. Shawn O. PearceFeb 28, 2007
  9. Brian GernhardtFeb 28, 2007
  10. Jakub NarebskiMar 1, 2007
  11. Matthieu MoyMar 1, 2007
  12. Shawn O. PearceMar 1, 2007
  13. Martin LanghoffMar 4, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.