What's cooking (2022/04 #04)
Junio C Hamano committed
Apr 14, 2022 at 14:55 UTC
e659541d82341d73cd7d6e1366ad3228d13d36ab
1 file changed
+58
-38
whats-cooking.txt
+58
-38
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
Bcc: lwn@lwn.net
3
-Subject: What's cooking in git.git (Apr 2022, #03; Tue, 12)
4
-X-master-at: 11cfe552610386954886543f5de87dcc49ad5735
5
-X-next-at: 64f902a358a9e80c900e2fb98bca7fe335154015
3
+Subject: What's cooking in git.git (Apr 2022, #04; Thu, 14)
4
+X-master-at: 4027e30c5395c9c1aeea85e99f51ac62f5148145
5
+X-next-at: 8af0fa9b8e9e4d9f3a9661b1fd1f8c8822364ea5
6
7
-What's cooking in git.git (Apr 2022, #03; Tue, 12)
7
+What's cooking in git.git (Apr 2022, #04; Thu, 14)
8
--------------------------------------------------
9
10
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)
18
'seen'. The ones marked with '.' do not appear in any of the
19
integration branches, but I am still holding onto them.
20
21
-Security releases for the 2.30-2.35 maintenance tracks have been
22
-tagged to address CVE-2022-24765, where multi-user machines with a
23
-shared "mob" directory a user can trick other users into running a
24
-command of their choice easily. The fix has been merged up to Git
25
-2.36-rc2 and also all integration branches above.
26
-
21
Copies of the source code to Git live in many repositories, and the
22
following is a list of the ones I push into or their mirrors. Some
23
repositories have only a subset of branches.
@@ -55,33 +49,39 @@ Release tarballs are available at:
49
--------------------------------------------------
50
[Graduated to 'master']
51
58
-* ja/i18n-fix-for-2.36 (2022-04-11) 1 commit
59
- (merged to 'next' on 2022-04-11 at 0953a117dc)
60
- + i18n: fix some badly formatted i18n strings
52
+* jc/relnotes-updates (2022-04-13) 2 commits
53
+ (merged to 'next' on 2022-04-14 at a19d9a5cc2)
54
+ + RelNotes: mention safe.directory
55
+ + RelNotes: clarify "bisect run unexecutable" tweak
56
+
57
+ Wording updates for 2.36 release notes.
58
+
59
+* jc/revert-ref-transaction-hook-changes (2022-04-13) 3 commits
60
+ (merged to 'next' on 2022-04-14 at 94ac0baec8)
61
+ + RelNotes: revert the description on the reverted topics
62
+ + Revert "fetch: increase test coverage of fetches"
63
+ + Revert "Merge branch 'ps/avoid-unnecessary-hook-invocation-with-packed-refs'"
64
62
- Fixes to some localizable strings.
63
- source: <pull.1212.git.1649705011178.gitgitgadget@gmail.com>
65
+ Revert the "deletion of a ref should not trigger transaction events
66
+ for loose and packed ref backends separately" that regresses the
67
+ behaviour when a ref is not modified since it was packed.
68
69
--------------------------------------------------
70
[New Topics]
71
68
-* pw/test-malloc-with-sanitize-address (2022-04-11) 1 commit
69
- - tests: make SANITIZE=address imply TEST_NO_MALLOC_CHECK
72
+* sa/t1011-use-helpers (2022-04-12) 1 commit
73
+ - t1011: replace test -f with test_path_is_file
74
71
- Avoid problems from interaction between malloc_check and address
72
- sanitizer.
75
+ A GSoC practice.
76
77
Will merge to 'next'.
75
- source: <pull.1210.git.1649507317350.gitgitgadget@gmail.com>
76
-
78
+ source: <20220412203722.10484-1-siddharthasthana31@gmail.com>
79
78
-* rs/t7812-pcre2-ws-bug-test (2022-04-11) 1 commit
79
- - t7812: test PCRE2 whitespace bug
80
81
- A test to ensure workaround for an earlier pcre2 bug does work.
81
+* ep/coverage-report-wants-test-to-have-run (2022-04-13) 1 commit
82
+ - Makefile: add a prerequisite to the coverage-report target
83
83
- Will merge to 'next'.
84
- source: <3a49649d-8ff9-e5a7-e3fd-33fee5068ae8@web.de>
84
+ source: <20220414022513.31465-1-gitter.spiros@gmail.com>
85
86
--------------------------------------------------
87
[Stalled]
@@ -138,6 +138,25 @@ Release tarballs are available at:
138
--------------------------------------------------
139
[Cooking]
140
141
+* pw/test-malloc-with-sanitize-address (2022-04-11) 1 commit
142
+ - tests: make SANITIZE=address imply TEST_NO_MALLOC_CHECK
143
+
144
+ Avoid problems from interaction between malloc_check and address
145
+ sanitizer.
146
+
147
+ Will merge to 'next'.
148
+ source: <pull.1210.git.1649507317350.gitgitgadget@gmail.com>
149
+
150
+
151
+* rs/t7812-pcre2-ws-bug-test (2022-04-11) 1 commit
152
+ - t7812: test PCRE2 whitespace bug
153
+
154
+ A test to ensure workaround for an earlier pcre2 bug does work.
155
+
156
+ Will merge to 'next'.
157
+ source: <3a49649d-8ff9-e5a7-e3fd-33fee5068ae8@web.de>
158
+
159
+
160
* ah/convert-warning-message (2022-04-08) 1 commit
161
- convert: clarify line ending conversion warning
162
@@ -259,7 +278,7 @@ Release tarballs are available at:
278
source: <20220406181320.16911-1-eantoranz@gmail.com>
279
280
262
-* ab/plug-leak-in-revisions (2022-04-03) 28 commits
281
+* ab/plug-leak-in-revisions (2022-04-13) 28 commits
282
- revisions API: add a TODO for diff_free(&revs->diffopt)
283
- revisions API: have release_revisions() release "topo_walk_info"
284
- revisions API: have release_revisions() release "date_mode"
@@ -292,11 +311,11 @@ Release tarballs are available at:
311
Plug the memory leaks from the trickiest API of all, the revision
312
walker.
313
295
- Will merge to 'next'?
296
- source: <cover-v5-00.27-00000000000-20220402T102002Z-avarab@gmail.com>
314
+ Will merge to 'next'.
315
+ source: <cover-v6-00.27-00000000000-20220413T195935Z-avarab@gmail.com>
316
317
299
-* ab/ci-github-workflow-markup (2022-03-27) 7 commits
318
+* ab/ci-github-workflow-markup (2022-04-14) 7 commits
319
- ci: call `finalize_test_case_output` a little later
320
- ci: use `--github-workflow-markup` in the GitHub workflow
321
- ci: optionally mark up output in the GitHub workflow
@@ -309,13 +328,15 @@ Release tarballs are available at:
328
Build a moral equivalent of js/ci-github-workflow-markup on top of
329
ab/ci-setup-simplify.
330
312
- How does this compare feature-wise with js/ci-github-workflow-markup?
313
- source: <RFC-cover-v3-0.6-00000000000-20220325T183946Z-avarab@gmail.com>
331
+ How well does this compare feature-wise with js/ci-github-workflow-markup?
332
+ source: <RFC-cover-v4-0.6-00000000000-20220413T195514Z-avarab@gmail.com>
333
334
316
-* ab/ci-setup-simplify (2022-03-27) 25 commits
335
+* ab/ci-setup-simplify (2022-04-14) 29 commits
336
+ - CI: make it easy to use ci/*.sh outside of CI
337
- CI: don't use "set -x" in "ci/lib.sh" output
338
- CI: set PYTHON_PATH setting for osx-{clang,gcc} into "$jobname" case
339
+ - CI: set SANITIZE=leak in MAKEFLAGS directly
340
- CI: set CC in MAKEFLAGS directly, don't add it to the environment
341
- CI: add more variables to MAKEFLAGS, except under vs-build
342
- CI: narrow down variable definitions in --build and --test
@@ -327,6 +348,7 @@ Release tarballs are available at:
348
- CI: split up and reduce "ci/test-documentation.sh"
349
- CI: invoke "make artifacts-tar" directly in windows-build
350
- CI: check ignored unignored build artifacts in "win[+VS] build" too
351
+ - ci/lib.sh: use "test" instead of "["
352
- CI: remove "run-build-and-tests.sh", run "make [test]" directly
353
- CI: export variables via a wrapper
354
- CI: consistently use "export" in ci/lib.sh
@@ -334,6 +356,7 @@ Release tarballs are available at:
356
- CI: have "static-analysis" run "check-builtins", not "documentation"
357
- CI: have "static-analysis" run a "make ci-static-analysis" target
358
- CI: don't have "git grep" invoke a pager in tree content check
359
+ - CI/lib.sh: stop adding leading whitespace to $MAKEFLAGS
360
- CI: remove unused Azure ci/* code
361
- CI: remove dead "tree skipping" code
362
- CI: remove more dead Travis CI support
@@ -344,11 +367,8 @@ Release tarballs are available at:
367
Drive more actions done in CI via the Makefile instead of shell
368
commands sprinkled in .github/workflows/main.yml
369
347
- Unless "doing more in Makefile" is fundamentally undesirable, I am
348
- inclined to take this, together with ab/ci-github-workflow-markup
349
- to replace js/ci-github-workflow-markup
350
- cf. <xmqq4k361a57.fsf@gitster.g>
351
- source: <cover-v2-00.25-00000000000-20220325T182534Z-avarab@gmail.com>
370
+ Will merge to 'next'?
371
+ source: <cover-v3-00.29-00000000000-20220413T194847Z-avarab@gmail.com>
372
373
374
* kf/p4-multiple-remotes (2022-03-21) 1 commit