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

Re: [GSoC] [PATCH] travis-ci: added clang static analysis

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 6, 2018, 01:27 UTC
Message-ID
<xmqqpo4i6lj0.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20180305200400.3769-1-sidm1999@gmail.com>
SiddharthaMishra <sidm1999@gmail.com> writes:
> Added a job to run clang static code analysis on the master and maint branch
>
> Signed-off-by: SiddharthaMishra <sidm1999@gmail.com>
> ---

Why on 'master' and 'maint' and not others? Quite frankly, I find this choice of branches rather odd, as these two branches are not where the real development happens. If we do not want to increase the number of jobs and limit the test only to a single branch, I would probably pick 'next', and if we can afford two, probably 'pu' and 'next'.

Previous: SiddharthaMishraNext: Siddhartha Mishra
Message 2 of 9 in “travis-ci: added clang static analysis”
  1. SiddharthaMishraMar 5, 2018
  2. Junio C HamanoMar 6, 2018
  3. Siddhartha MishraMar 6, 2018
  4. Johannes SchindelinMar 7, 2018
  5. Lars SchneiderMar 12, 2018
  6. Siddhartha MishraMar 13, 2018
  7. Siddhartha MishraMar 13, 2018
  8. Lars SchneiderApr 1, 2018
  9. Siddhartha MishraApr 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.