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

Re: [PATCH] compat/regex/regexec.c: Fix some sparse warnings

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
May 17, 2011, 22:52 UTC
Message-ID
<BANLkTimQ9N3kYP+fWj+ifnav67fBYo1-oA@mail.gmail.com>
In-Reply-To
<4DD2B304.90305@ramsay1.demon.co.uk>
On Tue, May 17, 2011 at 19:40, Ramsay Jones <ramsay@ramsay1.demon.co.uk> wrote:
> In particular, sparse issues the following warnings:

Aside from this specific change, I think it's a problem that we pull in external libraries, then apply patches to them that upstream would probably want, don't tell upstream, and will inevitably have to deal with conflict when we merge in new versions from upstream.

Maybe we should have some file with contact details for these compat libraries, and try to resolve issues with upstream if we need to apply patches like this one?

Previous: Ramsay JonesNext: Junio C Hamano
Message 2 of 3 in “compat/regex/regexec.c: Fix some sparse warnings”
  1. compat/regex/regexec.c: Fix some sparse warningsRamsay Jones, May 17, 2011
  2. Ævar Arnfjörð BjarmasonMay 17, 2011
  3. Junio C HamanoMay 18, 2011

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.