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

Re: [PATCH v2] Fix buffer overflow in config parser

From
Jeff King <peff@peff.net>
Date
Apr 15, 2009, 07:53 UTC
Message-ID
<20090415075352.GB23332@coredump.intra.peff.net>
In-Reply-To
<20090415075035.GA23332@coredump.intra.peff.net>
On Wed, Apr 15, 2009 at 03:50:35AM -0400, Jeff King wrote:
Show 5 quoted lines
>   2. Tests which happen to require perl as part of the testing.
> [...]
> Your usage falls into (2), none of which are marked (and if they are to
> be marked, then all of them should be, since there is otherwise no
> point).

I meant to add: it is still nice to avoid the use of perl in the test scripts if we can (and I think we can in this instance, as other responses have noted). If a patch were made to skip tests which use perl, then the fewer tests we have to skip, the better.

-Peff
Previous: Jeff KingNext: Junio C Hamano
Message 5 of 10 in “Fix buffer overflow in config parser”
  1. Fix buffer overflow in config parserThomas Jarosch, Apr 14, 2009
  2. Johannes SchindelinApr 14, 2009
  3. Thomas JaroschApr 14, 2009
  4. Jeff KingApr 15, 2009
  5. Jeff KingApr 15, 2009
  6. Junio C HamanoApr 14, 2009
  7. Johannes SixtApr 15, 2009
  8. Johannes SixtApr 15, 2009
  9. Fix buffer overflow in config parserThomas Jarosch, Apr 17, 2009
  10. Johannes SchindelinApr 17, 2009

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.