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

Re: [PATCH] pathspec.c: Fix some sparse warnings

From
Jeff King <peff@peff.net>
Date
Oct 29, 2012, 05:55 UTC
Message-ID
<20121029055500.GA4457@sigill.intra.peff.net>
In-Reply-To
<508D9EFF.3040900@ramsay1.demon.co.uk>
On Sun, Oct 28, 2012 at 09:09:19PM +0000, Ramsay Jones wrote:
Show 8 quoted lines
> I asked Adam to squash this patch into his 'as/check-ignore' branch
> when he next re-rolled the branch. However, it appears that you
> resubmitted that branch instead ... :-D
> 
> I don't know if this branch is ready to progress to next yet, but
> could somebody (yourself, Adam or Jeff?) please squash this into
> commit 1a88ae42 ("pathspec.c: move reusable code from builtin/add.c")
> before it hits next.

I squashed it into my version of as/check-ignore, but if we are expecting a re-roll, please everybody remember to include it.

-Peff
Previous: Adam Spiers
Message 3 of 3 in “pathspec.c: Fix some sparse warnings”
  1. pathspec.c: Fix some sparse warningsRamsay Jones, Oct 28, 2012
  2. Adam SpiersOct 28, 2012
  3. Jeff KingOct 29, 2012

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.