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

Re: [PATCH v2 0/2] Using sparse in a CI job

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 5, 2019, 18:08 UTC
Message-ID
<xmqqmunartv6.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<af361187-4d9d-2c41-0850-bf774d5523b2@ramsayjones.plus.com>
Ramsay Jones <ramsay@ramsayjones.plus.com> writes:
Show 6 quoted lines
> Changes in v2:
>
>   - Add a new patch #1, which removes an obsolete use of SPARSE_FLAGS
>   - Actually initialise the new SP_EXTRA_FLAGS variable
>   - Reword the commit message (now #2) to, hopefully, clarify the
>     usage of SPARSE_FLAGS and SP_EXTRA_FLAGS
Thanks.  Applied.
Previous: Ramsay Jones
Message 2 of 2 in “Using sparse in a CI job”
  1. 0/2 Using sparse in a CI jobRamsay Jones, Feb 5, 2019
  2. Junio C HamanoFeb 5, 2019

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.