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

Re: [PATCH] Makefile: enable -Wsparse-error for DEVELOPER build

From
Ramsay Jones <ramsay@ramsayjones.plus.com>
Date
Nov 4, 2020, 16:57 UTC
Message-ID
<67b3569c-453f-4e6a-502e-136f8f3d8df7@ramsayjones.plus.com>
In-Reply-To
<nycvar.QRO.7.76.6.2011041431370.18437@tvgsbejvaqbjf.bet>
On 04/11/2020 13:43, Johannes Schindelin wrote:
Show 22 quoted lines
> Hi Ramsay,
> 
> On Tue, 3 Nov 2020, Ramsay Jones wrote:
> 
>> On 02/11/2020 18:55, Junio C Hamano wrote:
>>
>>> CI builds already have enough stuff around invocation of "make test"
>>> etc., and it would be trivial to pass SPARSE_FLAGS from the command
>>> line when adding "make sparse" invocation to one of the scripts in ci/
>>> directory, so from that point of view, this patch is not needed for
>>> them, either.
>>
>> My concern was more about how the CI system obtains/installs/builds a
>> sufficiently new version of sparse. Otherwise, 'make sparse' won't do
>> very much. ;-)  As I said, I don't know what's involved in getting that
>> to work.
> 
> As mentioned in https://github.com/gitgitgadget/git/issues/345, there is a
> Pipeline that builds sparse packages for Ubuntu, ready for use in our CI
> build: https://dev.azure.com/git/git/_build?definitionId=10&_a=summary.
> Currently, it is scheduled to run every weekday at 5:00am (I assume that's
> UTC).

Oh-my! Has there been a CI 'make sparse' build since september last year? :-D I missed that! (I couldn't view the azure build summary given above - it just keeps asking for a user/password :( ).

ATB, Ramsay Jones

Previous: Johannes SchindelinNext: Junio C Hamano
Message 8 of 11 in “upload-pack.c: fix a sparse warning”
  1. upload-pack.c: fix a sparse warningRamsay Jones, Oct 31, 2020
  2. Makefile: enable -Wsparse-error for DEVELOPER buildJunio C Hamano, Oct 31, 2020
  3. Ramsay JonesNov 2, 2020
  4. Junio C HamanoNov 2, 2020
  5. Ramsay JonesNov 3, 2020
  6. Junio C HamanoNov 3, 2020
  7. Johannes SchindelinNov 4, 2020
  8. Ramsay JonesNov 4, 2020
  9. Junio C HamanoNov 4, 2020
  10. Ramsay JonesNov 4, 2020
  11. Josh SteadmonNov 2, 2020

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.