What's cooking (2022/04 #03)
Junio C Hamano committed
Apr 12, 2022 at 01:23 UTC
a081b42c76d3d342adf132d17c37a6374b4631bb
1 file changed
+105
-86
whats-cooking.txt
+105
-86
@@ -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, #02; Fri, 8)
4
-X-master-at: ab1f2765f78e75ee51dface57e1071b3b7f42b09
5
-X-next-at: be66c8963cc046090ab0eb1f750e71f594a2a4e4
3
+Subject: What's cooking in git.git (Apr 2022, #03; Tue, 12)
4
+X-master-at: 11cfe552610386954886543f5de87dcc49ad5735
5
+X-next-at: 64f902a358a9e80c900e2fb98bca7fe335154015
6
7
-What's cooking in git.git (Apr 2022, #02; Fri, 8)
7
+What's cooking in git.git (Apr 2022, #03; Tue, 12)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -18,8 +18,11 @@ 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
-I just tagged Git 2.36-rc1; thank you, everybody, who reported and
22
-fixed glitches in the -rc0 preview release.
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
27
Copies of the source code to Git live in many repositories, and the
28
following is a list of the ones I push into or their mirrors. Some
@@ -52,36 +55,95 @@ Release tarballs are available at:
55
--------------------------------------------------
56
[Graduated to 'master']
57
55
-* bc/csprng-mktemps (2022-04-06) 1 commit
56
- (merged to 'next' on 2022-04-06 at 5510589561)
57
- + git-compat-util: really support openssl as a source of entropy
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
61
59
- Build fix.
60
- source: <20220405042826.56vyilttx3lo4scv@carlos-mbp.lan>
62
+ Fixes to some localizable strings.
63
+ source: <pull.1212.git.1649705011178.gitgitgadget@gmail.com>
64
65
+--------------------------------------------------
66
+[New Topics]
67
63
-* ld/sparse-index-bash-completion (2022-04-08) 1 commit
64
- - t9902: split test to run on appropriate systems
68
+* pw/test-malloc-with-sanitize-address (2022-04-11) 1 commit
69
+ - tests: make SANITIZE=address imply TEST_NO_MALLOC_CHECK
70
66
- Test regression fix.
67
- source: <20220408095353.11183-1-adam@dinwoodie.org>
71
+ Avoid problems from interaction between malloc_check and address
72
+ sanitizer.
73
74
+ Will merge to 'next'.
75
+ source: <pull.1210.git.1649507317350.gitgitgadget@gmail.com>
76
70
-* tl/ls-tree-oid-only (2022-04-08) 1 commit
71
- - ls-tree doc: document interaction with submodules
77
73
- Docfix.
74
- source: <patch-1.1-183b9639ae7-20220408T155704Z-avarab@gmail.com>
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.
82
+
83
+ Will merge to 'next'.
84
+ source: <3a49649d-8ff9-e5a7-e3fd-33fee5068ae8@web.de>
85
86
--------------------------------------------------
77
-[New Topics]
87
+[Stalled]
88
+
89
+* ab/commit-plug-leaks (2022-02-16) 2 commits
90
+ - commit: use strbuf_release() instead of UNLEAK()
91
+ - commit: fix "author_ident" leak
92
+
93
+ Leakfixes in the top-level called-once function.
94
+
95
+ Expecting a reroll.
96
+ I think UNLEAK->strbuf_release() is a regression.
97
+ source: <cover-0.2-00000000000-20220216T081844Z-avarab@gmail.com>
98
+
99
+
100
+* dl/prompt-pick-fix (2022-03-25) 1 commit
101
+ . git-prompt: fix sequencer/todo detection
102
+
103
+ Fix shell prompt script (in contrib/) for those who set
104
+ rebase.abbreviateCommands; we failed to recognize that we were in a
105
+ multi-step cherry-pick session.
106
+
107
+ Is this even needed? How?
108
+ cf. <xmqqwngdzque.fsf@gitster.g>
109
+ source: <20220325145301.3370-1-danny0838@gmail.com>
110
+
111
+
112
+* es/superproject-aware-submodules (2022-03-09) 3 commits
113
+ . rev-parse: short-circuit superproject worktree when config unset
114
+ . introduce submodule.hasSuperproject record
115
+ . t7400-submodule-basic: modernize inspect() helper
116
+
117
+ A configuration variable in a repository tells if it is (or is not)
118
+ a submodule of a superproject.
119
+
120
+ Expecting a reroll.
121
+ cf. <kl6l4k45s7cb.fsf@chooglen-macbookpro.roam.corp.google.com>
122
+ source: <20220310004423.2627181-1-emilyshaffer@google.com>
123
+
124
+
125
+* cw/remote-object-info (2022-03-30) 5 commits
126
+ . fixup! transfer.advertiseObjectInfo: add object-info config
127
+ . fixup! object-info: add option for retrieving object info
128
+ . object-info: add option for retrieving object info
129
+ . transfer.advertiseObjectInfo: add object-info config
130
+ . fetch-pack: refactor packet writing and fetch options
131
+
132
+ Attempt to add a client component to talk with object-info
133
+ endpoint.
134
+
135
+ Expecting a reroll.
136
+ source: <20220328191112.3092139-1-calvinwan@google.com>
137
+
138
+--------------------------------------------------
139
+[Cooking]
140
141
* ah/convert-warning-message (2022-04-08) 1 commit
142
- convert: clarify line ending conversion warning
143
144
Update a few end-user facing messages around eol conversion.
145
84
- Will merge to 'next'?
146
+ Will merge to 'next'.
147
source: <20220408044154.9947-1-alexhenrie24@gmail.com>
148
149
@@ -100,7 +162,7 @@ Release tarballs are available at:
162
163
Remove unused includes.
164
103
- Will merge to 'next'?
165
+ Will merge to 'next'.
166
source: <20220331194436.58005-1-garrit@slashdev.space>
167
168
@@ -109,7 +171,7 @@ Release tarballs are available at:
171
172
Test script updates.
173
112
- Will merge to 'next'?
174
+ Will merge to 'next'.
175
source: <20220405134742.17526-2-khalid.masum.92@gmail.com>
176
177
@@ -118,7 +180,7 @@ Release tarballs are available at:
180
181
Small code clean-up.
182
121
- Will merge to 'next'?
183
+ Will merge to 'next'.
184
source: <pull.1111.v2.git.1649092211419.gitgitgadget@gmail.com>
185
186
@@ -128,7 +190,7 @@ Release tarballs are available at:
190
The commit summary shown after making a commit is matched to what
191
is given in "git status" not to use the break-rewrite heuristics.
192
131
- Will merge to 'next'?
193
+ Will merge to 'next'.
194
source: <c35bd0aa-2e46-e710-2b39-89f18bad0097@web.de>
195
196
@@ -137,7 +199,7 @@ Release tarballs are available at:
199
200
"git p4" update.
201
140
- Will merge to 'next'?
202
+ Will merge to 'next'.
203
source: <pull.1203.git.1649051436934.gitgitgadget@gmail.com>
204
205
@@ -146,7 +208,7 @@ Release tarballs are available at:
208
209
"git p4" update.
210
149
- Will merge to 'next'?
211
+ Will merge to 'next'.
212
source: <pull.1202.git.1649049054600.gitgitgadget@gmail.com>
213
214
@@ -155,51 +217,11 @@ Release tarballs are available at:
217
- run-command API: rename "env_array" to "env"
218
- cocci: add a rename of "struct child_process"'s "env_array" to "env"
219
158
- source: <cover-0.3-00000000000-20220406T104134Z-avarab@gmail.com>
159
-
160
---------------------------------------------------
161
-[Stalled]
162
-
163
-* dl/prompt-pick-fix (2022-03-25) 1 commit
164
- - git-prompt: fix sequencer/todo detection
165
-
166
- Fix shell prompt script (in contrib/) for those who set
167
- rebase.abbreviateCommands; we failed to recognize that we were in a
168
- multi-step cherry-pick session.
169
-
170
- Is this even needed? How?
171
- cf. <xmqqwngdzque.fsf@gitster.g>
172
- source: <20220325145301.3370-1-danny0838@gmail.com>
173
-
174
-
175
-* es/superproject-aware-submodules (2022-03-09) 3 commits
176
- . rev-parse: short-circuit superproject worktree when config unset
177
- . introduce submodule.hasSuperproject record
178
- . t7400-submodule-basic: modernize inspect() helper
179
-
180
- A configuration variable in a repository tells if it is (or is not)
181
- a submodule of a superproject.
182
-
183
- Expecting a reroll.
184
- cf. <kl6l4k45s7cb.fsf@chooglen-macbookpro.roam.corp.google.com>
185
- source: <20220310004423.2627181-1-emilyshaffer@google.com>
186
-
187
-
188
-* cw/remote-object-info (2022-03-30) 5 commits
189
- . fixup! transfer.advertiseObjectInfo: add object-info config
190
- . fixup! object-info: add option for retrieving object info
191
- . object-info: add option for retrieving object info
192
- . transfer.advertiseObjectInfo: add object-info config
193
- . fetch-pack: refactor packet writing and fetch options
194
-
195
- Attempt to add a client component to talk with object-info
196
- endpoint.
220
+ Rename .env_array member to .env in the child_process structure.
221
198
- Expecting a reroll.
199
- source: <20220328191112.3092139-1-calvinwan@google.com>
222
+ On hold.
223
+ source: <cover-0.3-00000000000-20220406T104134Z-avarab@gmail.com>
224
201
---------------------------------------------------
202
-[Cooking]
225
226
* ab/misc-cleanup (2022-04-01) 6 commits
227
(merged to 'next' on 2022-04-04 at c5fb674865)
@@ -222,7 +244,7 @@ Release tarballs are available at:
244
"git -v" and "git -h" are now understood as "git --version" and
245
"git --help".
246
225
- Will merge to 'next'?
247
+ Will merge to 'next'.
248
source: <20220331212709.36036-1-garrit@slashdev.space>
249
250
@@ -269,6 +291,8 @@ Release tarballs are available at:
291
292
Plug the memory leaks from the trickiest API of all, the revision
293
walker.
294
+
295
+ Will merge to 'next'?
296
source: <cover-v5-00.27-00000000000-20220402T102002Z-avarab@gmail.com>
297
298
@@ -285,7 +309,7 @@ Release tarballs are available at:
309
Build a moral equivalent of js/ci-github-workflow-markup on top of
310
ab/ci-setup-simplify.
311
288
- Waiting for discussion to settle.
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>
314
315
@@ -320,7 +344,10 @@ Release tarballs are available at:
344
Drive more actions done in CI via the Makefile instead of shell
345
commands sprinkled in .github/workflows/main.yml
346
323
- Waiting for discussion to settle.
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>
352
353
@@ -347,7 +374,7 @@ Release tarballs are available at:
374
source: <20220330191909.294610-1-greenfoo@u92.eu>
375
376
350
-* bc/stash-export (2022-04-03) 4 commits
377
+* bc/stash-export (2022-04-08) 4 commits
378
- builtin/stash: provide a way to import stashes from a ref
379
- builtin/stash: provide a way to export stashes to a ref
380
- builtin/stash: factor out revision parsing into a function
@@ -357,7 +384,7 @@ Release tarballs are available at:
384
commit to transfer it across repositories has been introduced.
385
386
Will merge to 'next'?
360
- source: <20220403182250.904933-1-sandals@crustytoothpaste.net>
387
+ source: <20220407215352.3491567-1-sandals@crustytoothpaste.net>
388
389
390
* ns/batch-fsync (2022-04-06) 13 commits
@@ -394,6 +421,9 @@ Release tarballs are available at:
421
- sparse-checkout: make --cone the default
422
- tests: stop assuming --no-cone is the default mode for sparse-checkout
423
424
+ Deprecate non-cone mode of the sparse-checkout feature.
425
+
426
+ Will merge to 'next'?
427
source: <pull.1148.v2.git.1647054681.gitgitgadget@gmail.com>
428
429
@@ -490,17 +520,6 @@ Release tarballs are available at:
520
source: <pull.985.v6.git.1648742535.gitgitgadget@gmail.com>
521
522
493
-* ab/commit-plug-leaks (2022-02-16) 2 commits
494
- - commit: use strbuf_release() instead of UNLEAK()
495
- - commit: fix "author_ident" leak
496
-
497
- Leakfixes in the top-level called-once function.
498
-
499
- Expecting a reroll.
500
- I think UNLEAK->strbuf_release() is a regression.
501
- source: <cover-0.2-00000000000-20220216T081844Z-avarab@gmail.com>
502
-
503
-
523
* jh/builtin-fsmonitor-part3 (2022-03-25) 28 commits
524
- t7527: test Unicode NFC/NFD handling on MacOS
525
- t/lib-unicode-nfc-nfd: helper prereqs for testing unicode nfc/nfd