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

[PATCH 0/2] sparse warning on next branch

From
Ramsay Jones <ramsay@ramsayjones.plus.com>
Date
Mar 2, 2018, 02:52 UTC
Message-ID
<dfdc1b9c-0d64-fde9-e84a-ca5bdf0d47ea@ramsayjones.plus.com>

Tonight's build had a sparse warning and an additional ./static-check.pl symbol appear on the 'next' branch. As you know, I like to catch these on the 'pu' branch before they graduate to 'next', but it seems that I missed these! :( (The 'pu' branch is quite noisy with regard to sparse and static-check.pl at the moment).

These patches were developed on top of 'next', however, I also tested them on top of commit fcfba37337 directly. (Note, this is branch 'ps/contains-id-error-message' merged at commit 9623d6817b).

Ramsay Jones (2):
  ref-filter: mark a file-local symbol as static
  parse-options: remove the unused parse_opt_commits() function
 parse-options-cb.c | 16 ----------------
 parse-options.h    |  1 -
 ref-filter.c       |  2 +-
 3 files changed, 1 insertion(+), 18 deletions(-)
-- 
2.16.0
Message 1 of 1 in “sparse warning on next branch”
  1. 0/2 sparse warning on next branchRamsay Jones, Mar 2, 2018

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.