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

Re: [PATCH 0/2] ci(GitHub): mark up compile errors, too

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 9, 2022, 23:56 UTC
Message-ID
<xmqqbkv1gzmy.fsf@gitster.g>
In-Reply-To
<pull.1253.git.1654774347.gitgitgadget@gmail.com>

"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com> writes:

Show 5 quoted lines
> Just like we mark up test failures, it makes sense to mark up compile
> errors, too.
>
> In a sense, it makes even more sense with compile errors than with test
> failures because we can link directly to the corresponding source code in
Absolutely ;-).
Previous: Junio C HamanoNext: Johannes Schindelin via GitGitGadget
Message 6 of 11 in “ci(GitHub): mark up compile errors, too”
  1. 0/2 ci(GitHub): mark up compile errors, tooJohannes Schindelin via GitGitGadget, Jun 9, 2022
  2. 1/2 ci(github): use grouping also in the `win-build` jobJohannes Schindelin via GitGitGadget, Jun 9, 2022
  3. 2/2 ci(github): also mark up compile errorsJohannes Schindelin via GitGitGadget, Jun 9, 2022
  4. Ævar Arnfjörð BjarmasonJun 9, 2022
  5. Junio C HamanoJun 10, 2022
  6. Junio C HamanoJun 9, 2022
  7. 0/2 ci(GitHub): mark up compile errors, tooJohannes Schindelin via GitGitGadget, Jun 13, 2022
  8. 2/2 ci(github): also mark up compile errorsJohannes Schindelin via GitGitGadget, Jun 13, 2022
  9. 1/2 ci(github): use grouping also in the `win-build` jobJohannes Schindelin via GitGitGadget, Jun 13, 2022
  10. Junio C HamanoJun 13, 2022
  11. Ævar Arnfjörð BjarmasonJun 13, 2022

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.