What's cooking (2022/04 #04)

diff --git a/whats-cooking.txt b/whats-cooking.txt
index 3e5da5adaa80314034c209d8318c7e9b08da178d..8d016062731d6bac35ed5670414997157440f4bc 100644 (file)
--- a/whats-cooking.txt
+++ b/whats-cooking.txt
@@ -1,10 +1,10 @@
 To: git@vger.kernel.org
 Bcc: lwn@lwn.net
-Subject: What's cooking in git.git (Apr 2022, #03; Tue, 12)
-X-master-at: 11cfe552610386954886543f5de87dcc49ad5735
-X-next-at: 64f902a358a9e80c900e2fb98bca7fe335154015
+Subject: What's cooking in git.git (Apr 2022, #04; Thu, 14)
+X-master-at: 4027e30c5395c9c1aeea85e99f51ac62f5148145
+X-next-at: 8af0fa9b8e9e4d9f3a9661b1fd1f8c8822364ea5
 
-What's cooking in git.git (Apr 2022, #03; Tue, 12)
+What's cooking in git.git (Apr 2022, #04; Thu, 14)
 --------------------------------------------------
 
 Here are the topics that have been cooking in my tree.  Commits
@@ -18,12 +18,6 @@ useful").  Do not read too much into a topic being in (or not in)
 'seen'.  The ones marked with '.' do not appear in any of the
 integration branches, but I am still holding onto them.
 
-Security releases for the 2.30-2.35 maintenance tracks have been
-tagged to address CVE-2022-24765, where multi-user machines with a
-shared "mob" directory a user can trick other users into running a
-command of their choice easily.  The fix has been merged up to Git
-2.36-rc2 and also all integration branches above.
-
 Copies of the source code to Git live in many repositories, and the
 following is a list of the ones I push into or their mirrors.  Some
 repositories have only a subset of branches.
@@ -55,33 +49,39 @@ Release tarballs are available at:
 --------------------------------------------------
 [Graduated to 'master']
 
-* ja/i18n-fix-for-2.36 (2022-04-11) 1 commit
-  (merged to 'next' on 2022-04-11 at 0953a117dc)
- + i18n: fix some badly formatted i18n strings
+* jc/relnotes-updates (2022-04-13) 2 commits
+  (merged to 'next' on 2022-04-14 at a19d9a5cc2)
+ + RelNotes: mention safe.directory
+ + RelNotes: clarify "bisect run unexecutable" tweak
+
+ Wording updates for 2.36 release notes.
+
+* jc/revert-ref-transaction-hook-changes (2022-04-13) 3 commits
+  (merged to 'next' on 2022-04-14 at 94ac0baec8)
+ + RelNotes: revert the description on the reverted topics
+ + Revert "fetch: increase test coverage of fetches"
+ + Revert "Merge branch 'ps/avoid-unnecessary-hook-invocation-with-packed-refs'"
 
- Fixes to some localizable strings.
- source: <pull.1212.git.1649705011178.gitgitgadget@gmail.com>
+ Revert the "deletion of a ref should not trigger transaction events
+ for loose and packed ref backends separately" that regresses the
+ behaviour when a ref is not modified since it was packed.
 
 --------------------------------------------------
 [New Topics]
 
-* pw/test-malloc-with-sanitize-address (2022-04-11) 1 commit
- - tests: make SANITIZE=address imply TEST_NO_MALLOC_CHECK
+* sa/t1011-use-helpers (2022-04-12) 1 commit
+ - t1011: replace test -f with test_path_is_file
 
- Avoid problems from interaction between malloc_check and address
- sanitizer.
+ A GSoC practice.
 
  Will merge to 'next'.
- source: <pull.1210.git.1649507317350.gitgitgadget@gmail.com>
-
+ source: <20220412203722.10484-1-siddharthasthana31@gmail.com>
 
-* rs/t7812-pcre2-ws-bug-test (2022-04-11) 1 commit
- - t7812: test PCRE2 whitespace bug
 
- A test to ensure workaround for an earlier pcre2 bug does work.
+* ep/coverage-report-wants-test-to-have-run (2022-04-13) 1 commit
+ - Makefile: add a prerequisite to the coverage-report target
 
- Will merge to 'next'.
- source: <3a49649d-8ff9-e5a7-e3fd-33fee5068ae8@web.de>
+ source: <20220414022513.31465-1-gitter.spiros@gmail.com>
 
 --------------------------------------------------
 [Stalled]
@@ -138,6 +138,25 @@ Release tarballs are available at:
 --------------------------------------------------
 [Cooking]
 
+* pw/test-malloc-with-sanitize-address (2022-04-11) 1 commit
+ - tests: make SANITIZE=address imply TEST_NO_MALLOC_CHECK
+
+ Avoid problems from interaction between malloc_check and address
+ sanitizer.
+
+ Will merge to 'next'.
+ source: <pull.1210.git.1649507317350.gitgitgadget@gmail.com>
+
+
+* rs/t7812-pcre2-ws-bug-test (2022-04-11) 1 commit
+ - t7812: test PCRE2 whitespace bug
+
+ A test to ensure workaround for an earlier pcre2 bug does work.
+
+ Will merge to 'next'.
+ source: <3a49649d-8ff9-e5a7-e3fd-33fee5068ae8@web.de>
+
+
 * ah/convert-warning-message (2022-04-08) 1 commit
  - convert: clarify line ending conversion warning
 
@@ -259,7 +278,7 @@ Release tarballs are available at:
  source: <20220406181320.16911-1-eantoranz@gmail.com>
 
 
-* ab/plug-leak-in-revisions (2022-04-03) 28 commits
+* ab/plug-leak-in-revisions (2022-04-13) 28 commits
  - revisions API: add a TODO for diff_free(&revs->diffopt)
  - revisions API: have release_revisions() release "topo_walk_info"
  - revisions API: have release_revisions() release "date_mode"
@@ -292,11 +311,11 @@ Release tarballs are available at:
  Plug the memory leaks from the trickiest API of all, the revision
  walker.
 
- Will merge to 'next'?
- source: <cover-v5-00.27-00000000000-20220402T102002Z-avarab@gmail.com>
+ Will merge to 'next'.
+ source: <cover-v6-00.27-00000000000-20220413T195935Z-avarab@gmail.com>
 
 
-* ab/ci-github-workflow-markup (2022-03-27) 7 commits
+* ab/ci-github-workflow-markup (2022-04-14) 7 commits
  - ci: call `finalize_test_case_output` a little later
  - ci: use `--github-workflow-markup` in the GitHub workflow
  - ci: optionally mark up output in the GitHub workflow
@@ -309,13 +328,15 @@ Release tarballs are available at:
  Build a moral equivalent of js/ci-github-workflow-markup on top of
  ab/ci-setup-simplify.
 
- How does this compare feature-wise with js/ci-github-workflow-markup?
- source: <RFC-cover-v3-0.6-00000000000-20220325T183946Z-avarab@gmail.com>
+ How well does this compare feature-wise with js/ci-github-workflow-markup?
+ source: <RFC-cover-v4-0.6-00000000000-20220413T195514Z-avarab@gmail.com>
 
 
-* ab/ci-setup-simplify (2022-03-27) 25 commits
+* ab/ci-setup-simplify (2022-04-14) 29 commits
+ - CI: make it easy to use ci/*.sh outside of CI
  - CI: don't use "set -x" in "ci/lib.sh" output
  - CI: set PYTHON_PATH setting for osx-{clang,gcc} into "$jobname" case
+ - CI: set SANITIZE=leak in MAKEFLAGS directly
  - CI: set CC in MAKEFLAGS directly, don't add it to the environment
  - CI: add more variables to MAKEFLAGS, except under vs-build
  - CI: narrow down variable definitions in --build and --test
@@ -327,6 +348,7 @@ Release tarballs are available at:
  - CI: split up and reduce "ci/test-documentation.sh"
  - CI: invoke "make artifacts-tar" directly in windows-build
  - CI: check ignored unignored build artifacts in "win[+VS] build" too
+ - ci/lib.sh: use "test" instead of "["
  - CI: remove "run-build-and-tests.sh", run "make [test]" directly
  - CI: export variables via a wrapper
  - CI: consistently use "export" in ci/lib.sh
@@ -334,6 +356,7 @@ Release tarballs are available at:
  - CI: have "static-analysis" run "check-builtins", not "documentation"
  - CI: have "static-analysis" run a "make ci-static-analysis" target
  - CI: don't have "git grep" invoke a pager in tree content check
+ - CI/lib.sh: stop adding leading whitespace to $MAKEFLAGS
  - CI: remove unused Azure ci/* code
  - CI: remove dead "tree skipping" code
  - CI: remove more dead Travis CI support
@@ -344,11 +367,8 @@ Release tarballs are available at:
  Drive more actions done in CI via the Makefile instead of shell
  commands sprinkled in .github/workflows/main.yml
 
- Unless "doing more in Makefile" is fundamentally undesirable, I am
- inclined to take this, together with ab/ci-github-workflow-markup
- to replace js/ci-github-workflow-markup
- cf. <xmqq4k361a57.fsf@gitster.g>
- source: <cover-v2-00.25-00000000000-20220325T182534Z-avarab@gmail.com>
+ Will merge to 'next'?
+ source: <cover-v3-00.29-00000000000-20220413T194847Z-avarab@gmail.com>
 
 
 * kf/p4-multiple-remotes (2022-03-21) 1 commit