{"thread":{"id":"47956","subject":"[PATCH 0/2] sparse warning on next branch","startedAt":"2018-03-02T02:52:37Z","lastAt":"2018-03-02T02:52:37Z","messageCount":1,"participants":["Ramsay Jones"],"isPatch":true,"patchVersion":1,"patchTotal":2},"messages":[{"id":"340776","messageId":"dfdc1b9c-0d64-fde9-e84a-ca5bdf0d47ea@ramsayjones.plus.com","threadId":"47956","inReplyTo":null,"subject":"[PATCH 0/2] sparse warning on next branch","fromName":"Ramsay Jones","fromEmail":"ramsay@ramsayjones.plus.com","sentAt":"2018-03-02T02:52:27Z","receivedAt":"2018-03-02T02:52:37Z","isPatch":true,"sender":{"key":"ramsay@ramsayjones.plus.com","avatar":"https://avatars.githubusercontent.com/u/33702710?v=4"},"body":"\nTonight's build had a sparse warning and an additional ./static-check.pl\nsymbol appear on the 'next' branch. As you know, I like to catch these\non the 'pu' branch before they graduate to 'next', but it seems that I\nmissed these! :( (The 'pu' branch is quite noisy with regard to sparse\nand static-check.pl at the moment).\n\nThese patches were developed on top of 'next', however, I also tested\nthem on top of commit fcfba37337 directly. (Note, this is branch\n'ps/contains-id-error-message' merged at commit 9623d6817b).\n\nRamsay Jones (2):\n  ref-filter: mark a file-local symbol as static\n  parse-options: remove the unused parse_opt_commits() function\n\n parse-options-cb.c | 16 ----------------\n parse-options.h    |  1 -\n ref-filter.c       |  2 +-\n 3 files changed, 1 insertion(+), 18 deletions(-)\n\n-- \n2.16.0\n"}]}