From: Victoria Dye <vdye@github.com>
To: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Derrick Stolee <derrickstolee@github.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: What's cooking in git.git (May 2022, #07; Wed, 25)
Date: Thu, 26 May 2022 09:02:27 -0700 [thread overview]
Message-ID: <df44b0cd-bba7-19f0-4e45-c0988239cc4d@github.com> (raw)
In-Reply-To: <xmqqzgj41ya2.fsf@gitster.g>
Junio C Hamano wrote:
> * 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'.
> * ds/sparse-sparse-checkout (2022-05-23) 10 commits
> - sparse-checkout: integrate with sparse index
> - p2000: add test for 'git sparse-checkout [add|set]'
> - sparse-index: complete partial expansion
> - sparse-index: partially expand directories
> - sparse-checkout: --no-sparse-index needs a full index
> - cache-tree: implement cache_tree_find_path()
> - sparse-index: introduce partially-sparse indexes
> - sparse-index: create expand_index()
> - t1092: stress test 'git sparse-checkout set'
> - t1092: refactor 'sparse-index contents' test
>
> "sparse-checkout" learns to work well with the sparse-index
> feature.
>
> Will merge to 'next'?
> source: <pull.1208.v3.git.1653313726.gitgitgadget@gmail.com>
>
Likewise here - V2 handled all of my nits, and V3 made some helpful
improvements to variable naming & documentation. There's nothing else I'm
waiting for on this, so I'd be happy to see it merge to 'next'.
next prev parent reply other threads:[~2022-05-26 16:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 8:41 What's cooking in git.git (May 2022, #07; Wed, 25) Junio C Hamano
2022-05-26 16:02 ` Victoria Dye [this message]
2022-05-26 17:23 ` Junio C Hamano
2022-05-26 18:02 ` Ævar Arnfjörð Bjarmason
2022-05-26 18:30 ` Victoria Dye
2022-05-26 18:40 ` Ævar Arnfjörð Bjarmason
2022-05-26 23:10 ` Junio C Hamano
2022-05-26 18:08 ` tb/cruft-packs (was Re: What's cooking in git.git (May 2022, #07; Wed, 25)) Taylor Blau
2022-05-26 18:10 ` What's cooking in git.git (May 2022, #07; Wed, 25) Taylor Blau
2022-05-26 20:17 ` Junio C Hamano
2022-05-26 18:11 ` tb/midx-race-in-pack-objects (was Re: What's cooking in git.git (May 2022, #07; Wed, 25)) Taylor Blau
2022-05-26 18:49 ` sg/build-gitweb (was: " Ævar Arnfjörð Bjarmason
2022-05-26 19:06 ` sg/build-gitweb Junio C Hamano
2022-05-26 18:51 ` jc/http-clear-finished-pointer (was: What's cooking in git.git (May 2022, #07; Wed, 25)) Ævar Arnfjörð Bjarmason
2022-05-26 19:37 ` Re* jc/http-clear-finished-pointer Junio C Hamano
2022-05-27 20:41 ` Johannes Schindelin
2022-05-27 21:35 ` Junio C Hamano
2022-06-01 7:26 ` Ævar Arnfjörð Bjarmason
2022-06-01 15:48 ` Junio C Hamano
2022-05-26 18:54 ` js/bisect-in-c (was: What's cooking in git.git (May 2022, #07; Wed, 25)) Ævar Arnfjörð Bjarmason
2022-05-26 19:38 ` js/bisect-in-c Junio C Hamano
2022-05-26 20:00 ` js/bisect-in-c Junio C Hamano
2022-05-27 12:52 ` js/bisect-in-c Ævar Arnfjörð Bjarmason
2022-05-26 18:57 ` jx/l10n-workflow-change (was: What's cooking in git.git (May 2022, #07; Wed, 25)) Ævar Arnfjörð Bjarmason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=df44b0cd-bba7-19f0-4e45-c0988239cc4d@github.com \
--to=vdye@github.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).