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

Re: What's cooking in git.git (May 2022, #07; Wed, 25)

From
Junio C Hamano <gitster@pobox.com>
Date
May 26, 2022, 17:23 UTC
Message-ID
<xmqq4k1c1a34.fsf@gitster.g>
In-Reply-To
<df44b0cd-bba7-19f0-4e45-c0988239cc4d@github.com>
Victoria Dye <vdye@github.com> writes:
Show 27 quoted lines
>> * js/ci-github-workflow-markup (2022-05-21) 12 commits
>>  - ci: call `finalize_test_case_output` a little later
>>  - ci(github): mention where the full logs can be found
>>  - ci: use `--github-workflow-markup` in the GitHub workflow
>>  - ci(github): avoid printing test case preamble twice
>>  - ci(github): skip the logs of the successful test cases
>>  - ci: optionally mark up output in the GitHub workflow
>>  - ci/run-build-and-tests: add some structure to the GitHub workflow output
>>  - ci: make it easier to find failed tests' logs in the GitHub workflow
>>  - ci/run-build-and-tests: take a more high-level view
>>  - test(junit): avoid line feeds in XML attributes
>>  - tests: refactor --write-junit-xml code
>>  - ci: fix code style
>> 
>>  Update the GitHub workflow support to make it quicker to get to the
>>  failing test.
>> 
>>  Will merge to 'next'?
>>  source: <pull.1117.v3.git.1653171536.gitgitgadget@gmail.com>
>
> The latest version of this nicely addressed the feedback I originally had,
> particularly in improving page loading time. It's still slower than before
> this series, but IMO it's manageable (especially taking into account the
> improved information accessibility). 
>
> I don't see (or have) any other unaddressed concerns, so I'm in favor of
> moving it to 'next'.

I see Ævar sent another reroll of "rebuild the base" and "then rebase a (hopefully) equivalent of this series on top", but I think it is unhealthy to keep doing that. Does the latest "rebuild the base" part look unsalvageably and fundamentally bad that it is not worth our time to consider joining forces to polish it sufficiently and then build this on top?

If that is the case, then I am OK to merge this to 'next' to cast it in stone, and then the let "rebuild the base" part once die, to be reborn as many "tweak the way things work to (clarify|optimize) X" follow-up topics.

Thanks.
Previous: Victoria DyeNext: Ævar Arnfjörð Bjarmason
Message 3 of 24 in “What's cooking in git.git (May 2022, #07; Wed, 25)”
  1. Junio C HamanoMay 26, 2022
  2. Victoria DyeMay 26, 2022
  3. Junio C HamanoMay 26, 2022
  4. Ævar Arnfjörð BjarmasonMay 26, 2022
  5. Victoria DyeMay 26, 2022
  6. Ævar Arnfjörð BjarmasonMay 26, 2022
  7. Junio C HamanoMay 26, 2022
  8. tb/cruft-packs (was Re: What's cooking in git.git (May 2022, #07; Wed, 25))Taylor Blau, May 26, 2022
  9. Taylor BlauMay 26, 2022
  10. Junio C HamanoMay 26, 2022
  11. tb/midx-race-in-pack-objects (was Re: What's cooking in git.git (May 2022, #07; Wed, 25))Taylor Blau, May 26, 2022
  12. sg/build-gitweb (was: What's cooking in git.git (May 2022, #07; Wed, 25))Ævar Arnfjörð Bjarmason, May 26, 2022
  13. Junio C HamanoMay 26, 2022
  14. jc/http-clear-finished-pointer (was: What's cooking in git.git (May 2022, #07; Wed, 25))Ævar Arnfjörð Bjarmason, May 26, 2022
  15. Re* jc/http-clear-finished-pointerJunio C Hamano, May 26, 2022
  16. Johannes SchindelinMay 27, 2022
  17. Junio C HamanoMay 27, 2022
  18. Ævar Arnfjörð BjarmasonJun 1, 2022
  19. Junio C HamanoJun 1, 2022
  20. js/bisect-in-c (was: What's cooking in git.git (May 2022, #07; Wed, 25))Ævar Arnfjörð Bjarmason, May 26, 2022
  21. Junio C HamanoMay 26, 2022
  22. Junio C HamanoMay 26, 2022
  23. Ævar Arnfjörð BjarmasonMay 27, 2022
  24. jx/l10n-workflow-change (was: What's cooking in git.git (May 2022, #07; Wed, 25))Ævar Arnfjörð Bjarmason, May 26, 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.