What's cooking (2024/05 #08)
Junio C Hamano committed
May 20, 2024 at 13:22 UTC
2bf25d958cc456216107161d76387cd1cc669ef1
1 file changed
+109
-218
whats-cooking.txt
+109
-218
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (May 2024, #07; Fri, 17)
3
-X-master-at: d8ab1d464d07baa30e5a180eb33b3f9aa5c93adf
4
-X-next-at: de53f37879660c0da62a72472ba37f8680a3587c
2
+Subject: What's cooking in git.git (May 2024, #08; Mon, 20)
3
+X-master-at: 4365c6fcf96caac73dcc412aa25db34cf8df48d5
4
+X-next-at: 888b28324335471fe2b21105063128ca8fa54801
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (May 2024, #07; Fri, 17)
7
+What's cooking in git.git (May 2024, #08; Mon, 20)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -46,159 +46,74 @@ Release tarballs are available at:
46
https://www.kernel.org/pub/software/scm/git/
47
48
--------------------------------------------------
49
-[Graduated to 'master']
50
-
51
-* ds/scalar-reconfigure-all-fix (2024-05-07) 1 commit
52
- (merged to 'next' on 2024-05-08 at eca398f4a5)
53
- + scalar: avoid segfault in reconfigure --all
54
-
55
- Scalar fix.
56
- source: <pull.1724.v3.git.1715126749391.gitgitgadget@gmail.com>
57
-
58
-
59
-* jl/git-no-advice (2024-05-07) 4 commits
60
- (merged to 'next' on 2024-05-08 at c9e7e0866e)
61
- + t0018: two small fixes
62
- (merged to 'next' on 2024-05-06 at 95cc03ef96)
63
- + advice: add --no-advice global option
64
- + doc: add spacing around paginate options
65
- + doc: clean up usage documentation for --no-* opts
66
-
67
- A new global "--no-advice" option can be used to disable all advice
68
- messages, which is meant to be used only in scripts.
69
- source: <20240503071706.78109-1-james@jamesliu.io>
70
-
71
-
72
-* jp/tag-trailer (2024-05-07) 3 commits
73
- (merged to 'next' on 2024-05-07 at 646013793d)
74
- + builtin/tag: add --trailer option
75
- + builtin/commit: refactor --trailer logic
76
- + builtin/commit: use ARGV macro to collect trailers
77
-
78
- "git tag" learned the "--trailer" option to futz with the trailers
79
- in the same way as "git commit" does.
80
- source: <pull.1723.v5.git.1714934950.gitgitgadget@gmail.com>
81
-
49
+[New Topics]
50
83
-* js/unit-test-suite-runner (2024-05-06) 9 commits
84
- (merged to 'next' on 2024-05-07 at 3b376223e3)
85
- + cmake: let `test-tool` run the unit tests, too
86
- + ci: use test-tool as unit test runner on Windows
87
- + t/Makefile: run unit tests alongside shell tests
88
- + unit tests: add rule for running with test-tool
89
- + test-tool run-command testsuite: support unit tests
90
- + test-tool run-command testsuite: remove hardcoded filter
91
- + test-tool run-command testsuite: get shell from env
92
- + t0080: turn t-basic unit test into a helper
93
- + Merge branch 'jk/unit-tests-buildfix' into js/unit-test-suite-runner
51
+* es/chainlint-ncores-fix (2024-05-20) 3 commits
52
+ - chainlint.pl: latch CPU count directly reported by /proc/cpuinfo
53
+ - chainlint.pl: fix incorrect CPU count on Linux SPARC
54
+ - chainlint.pl: make CPU count computation more robust
55
95
- The "test-tool" has been taught to run testsuite tests in parallel,
96
- bypassing the need to use the "prove" tool.
97
- source: <cover.1715024899.git.steadmon@google.com>
98
- source: <pull.1666.git.1708038924522.gitgitgadget@gmail.com>
56
+ The chainlint script (invoked during "make test") did nothing when
57
+ it failed to detect the number of available CPUs. It now falls
58
+ back to 1 CPU to avoid the problem.
59
60
+ Will merge to 'next'.
61
+ source: <20240520190131.94904-1-ericsunshine@charter.net>
62
101
-* jt/port-ci-whitespace-check-to-gitlab (2024-05-03) 5 commits
102
- (merged to 'next' on 2024-05-08 at 774a29dde4)
103
- + gitlab-ci: add whitespace error check
104
- + ci: make the whitespace report optional
105
- + ci: separate whitespace check script
106
- + github-ci: fix link to whitespace error
107
- + ci: pre-collapse GitLab CI sections
63
+--------------------------------------------------
64
+[Graduated to 'master']
65
109
- The "whitespace check" task that was enabled for GitHub Actions CI
110
- has been ported to GitLab CI.
111
- source: <20240503172110.181326-1-jltobler@gmail.com>
66
+* jc/compat-regex-calloc-fix (2024-05-13) 1 commit
67
+ (merged to 'next' on 2024-05-13 at 077c4e1dcc)
68
+ + compat/regex: fix argument order to calloc(3)
69
70
+ Windows CI running in GitHub Actions started complaining about the
71
+ order of arguments given to calloc(); the imported regex code uses
72
+ the wrong order almost consistently, which has been corrected.
73
+ source: <xmqqbk5bim2n.fsf@gitster.g>
74
114
-* ow/refspec-glossary-update (2024-05-06) 1 commit
115
- (merged to 'next' on 2024-05-07 at 7d55ebb0c8)
116
- + Documentation: Mention that refspecs are explained elsewhere
75
118
- Doc update.
119
- source: <20240506182317.13477-1-oystwa@gmail.com>
120
-
121
-
122
-* ps/config-subcommands (2024-05-06) 14 commits
123
- (merged to 'next' on 2024-05-07 at f10c689a30)
124
- + builtin/config: display subcommand help
125
- + builtin/config: introduce "edit" subcommand
126
- + builtin/config: introduce "remove-section" subcommand
127
- + builtin/config: introduce "rename-section" subcommand
128
- + builtin/config: introduce "unset" subcommand
129
- + builtin/config: introduce "set" subcommand
130
- + builtin/config: introduce "get" subcommand
131
- + builtin/config: introduce "list" subcommand
132
- + builtin/config: pull out function to handle `--null`
133
- + builtin/config: pull out function to handle config location
134
- + builtin/config: use `OPT_CMDMODE()` to specify modes
135
- + builtin/config: move "fixed-value" option to correct group
136
- + builtin/config: move option array around
137
- + config: clarify memory ownership when preparing comment strings
138
- (this branch is used by ps/builtin-config-cleanup.)
139
-
140
- The operation mode options (like "--get") the "git config" command
141
- uses have been deprecated and replaced with subcommands (like "git
142
- config get").
143
- source: <cover.1714982328.git.ps@pks.im>
144
-
145
-
146
-* ps/refs-without-the-repository (2024-05-07) 5 commits
147
- (merged to 'next' on 2024-05-08 at 2479b9de46)
148
- + refs: remove functions without ref store
149
- + cocci: apply rules to rewrite callers of "refs" interfaces
150
- + cocci: introduce rules to transform "refs" to pass ref store
151
- + refs: add `exclude_patterns` parameter to `for_each_fullref_in()`
152
- + refs: introduce missing functions that accept a `struct ref_store`
153
- (this branch is used by ps/refs-without-the-repository-updates.)
154
-
155
- The refs API lost functions that implicitly assumes to work on the
156
- primary ref_store by forcing the callers to pass a ref_store as an
157
- argument.
158
- source: <cover.1715065736.git.ps@pks.im>
159
-
160
-
161
-* rs/external-diff-with-exit-code (2024-05-06) 1 commit
162
- (merged to 'next' on 2024-05-08 at ad5fee3cbf)
163
- + diff: report unmerged paths as changes in run_diff_cmd()
164
-
165
- The "--exit-code" option of "git diff" command learned to report
166
- unmerged paths as changes.
167
-
168
- [jc: the tip one was reverted out]
169
- source: <82561c70-ec33-41bf-b036-52310ffc1926@web.de>
170
-
171
-
172
-* vd/doc-merge-tree-x-option (2024-05-07) 1 commit
173
- (merged to 'next' on 2024-05-08 at 42637b8bdf)
174
- + Documentation/git-merge-tree.txt: document -X
76
+* kn/ref-transaction-symref (2024-05-07) 8 commits
77
+ (merged to 'next' on 2024-05-11 at 0a7119f2a3)
78
+ + refs: remove `create_symref` and associated dead code
79
+ + refs: rename `refs_create_symref()` to `refs_update_symref()`
80
+ + refs: use transaction in `refs_create_symref()`
81
+ + refs: add support for transactional symref updates
82
+ + refs: move `original_update_refname` to 'refs.c'
83
+ + refs: support symrefs in 'reference-transaction' hook
84
+ + files-backend: extract out `create_symref_lock()`
85
+ + refs: accept symref values in `ref_transaction_update()`
86
+ (this branch is used by kn/update-ref-symref.)
87
176
- Doc update.
177
- source: <pull.1728.git.1715117789985.gitgitgadget@gmail.com>
88
+ Updates to symbolic refs can now be made as a part of ref
89
+ transaction.
90
+ source: <20240507125859.132116-1-knayak@gitlab.com>
91
92
--------------------------------------------------
180
-[New Topics]
93
+[Cooking]
94
95
* tb/pack-bitmap-write-cleanups (2024-05-15) 6 commits
183
- - pack-bitmap: introduce `bitmap_writer_free()`
184
- - pack-bitmap-write.c: avoid uninitialized 'write_as' field
185
- - pack-bitmap: drop unused `max_bitmaps` parameter
186
- - pack-bitmap: avoid use of static `bitmap_writer`
187
- - pack-bitmap-write.c: move commit_positions into commit_pos fields
188
- - object.h: add flags allocated by pack-bitmap.h
96
+ (merged to 'next' on 2024-05-20 at 585e7bde21)
97
+ + pack-bitmap: introduce `bitmap_writer_free()`
98
+ + pack-bitmap-write.c: avoid uninitialized 'write_as' field
99
+ + pack-bitmap: drop unused `max_bitmaps` parameter
100
+ + pack-bitmap: avoid use of static `bitmap_writer`
101
+ + pack-bitmap-write.c: move commit_positions into commit_pos fields
102
+ + object.h: add flags allocated by pack-bitmap.h
103
104
The pack bitmap code saw some clean-up to prepare for a follow-up topic.
105
192
- Will merge to 'next'?
106
+ Will merge to 'master'.
107
source: <cover.1715716605.git.me@ttaylorr.com>
108
109
110
* jc/t0017-clarify-bogus-expectation (2024-05-16) 1 commit
197
- - t0017: clarify dubious test set-up
111
+ (merged to 'next' on 2024-05-20 at c64016ec43)
112
+ + t0017: clarify dubious test set-up
113
114
Test clean-up.
115
201
- Will merge to 'next'?
116
+ Will merge to 'master'.
117
source: <xmqqcypmx44l.fsf@gitster.g>
118
119
@@ -222,7 +137,6 @@ Release tarballs are available at:
137
- update-ref: add support for 'symref-verify' command
138
- refs: create and use `ref_update_ref_must_exist()`
139
- Merge branch 'kn/ref-transaction-symref' into kn/update-ref-symref
225
- (this branch uses kn/ref-transaction-symref.)
140
141
"git update-ref --stdin" learned to handle transactional updates of
142
symbolic-refs.
@@ -233,22 +147,24 @@ Release tarballs are available at:
147
148
149
* mt/t0211-typofix (2024-05-16) 1 commit
236
- - t/t0211-trace2-perf.sh: fix typo patern -> pattern
150
+ (merged to 'next' on 2024-05-20 at f4fba3c7d2)
151
+ + t/t0211-trace2-perf.sh: fix typo patern -> pattern
152
153
Test fix.
154
240
- Will merge to 'next'.
155
+ Will merge to 'master'.
156
source: <ZkW5ggOVlglfi64u@telcontar>
157
158
159
* ps/complete-config-w-subcommands (2024-05-17) 1 commit
245
- - completion: adapt git-config(1) to complete subcommands
160
+ (merged to 'next' on 2024-05-20 at 14453d34fc)
161
+ + completion: adapt git-config(1) to complete subcommands
162
163
Update the command line completion script (in contrib/) to adjust
164
to the recent update to "git config" that adopted subcommand based
165
UI.
166
251
- Will merge to 'next'.
167
+ Will merge to 'master'.
168
source: <8d43dee33289969a5afbbf7635ac40b7312d8e19.1715926344.git.ps@pks.im>
169
170
@@ -280,23 +196,25 @@ Release tarballs are available at:
196
197
198
* jc/doc-diff-name-only (2024-05-17) 1 commit
283
- - diff: document what --name-only shows
199
+ (merged to 'next' on 2024-05-20 at 13b6f9350d)
200
+ + diff: document what --name-only shows
201
202
The documentation for "git diff --name-only" has been clarified
203
that it is about showing the names in the post-image tree.
204
288
- Will merge to 'next'.
205
+ Will merge to 'master'.
206
source: <xmqqeda0jr7d.fsf@gitster.g>
207
208
209
* kn/patch-iteration-doc (2024-05-17) 2 commits
293
- - SubmittingPatches: add section for iterating patches
294
- - Merge branch 'jc/patch-flow-updates' into kn/patch-iteration-doc
210
+ (merged to 'next' on 2024-05-20 at e0ee0051a9)
211
+ + SubmittingPatches: add section for iterating patches
212
+ + Merge branch 'jc/patch-flow-updates' into kn/patch-iteration-doc
213
(this branch uses jc/patch-flow-updates.)
214
215
Doc updates.
216
299
- Will merge to 'next'.
217
+ Will merge to 'master'.
218
source: <20240517122724.270706-1-knayak@gitlab.com>
219
220
@@ -337,20 +255,6 @@ Release tarballs are available at:
255
The project decision making policy has been documented.
256
source: <10f217915600eda3ebec886e4f020f87c22e318a.1715978031.git.steadmon@google.com>
257
340
---------------------------------------------------
341
-[Cooking]
342
-
343
-* jc/compat-regex-calloc-fix (2024-05-13) 1 commit
344
- (merged to 'next' on 2024-05-13 at 077c4e1dcc)
345
- + compat/regex: fix argument order to calloc(3)
346
-
347
- Windows CI running in GitHub Actions started complaining about the
348
- order of arguments given to calloc(); the imported regex code uses
349
- the wrong order almost consistently, which has been corrected.
350
-
351
- Will merge to 'master'.
352
- source: <xmqqbk5bim2n.fsf@gitster.g>
353
-
258
259
* jc/undecided-is-not-necessarily-sha1-fix (2024-05-16) 6 commits
260
- apply: fix uninitialized hash function
@@ -367,7 +271,8 @@ Release tarballs are available at:
271
the "default is sha-1" behaviour as an escape hatch, and start
272
fixing these breakages.
273
370
- Comments?
274
+ Broken.
275
+ The hash-object test does not seem to work with SHA-256 repositories.
276
source: <20240513224127.2042052-1-gitster@pobox.com>
277
278
@@ -392,43 +297,45 @@ Release tarballs are available at:
297
298
299
* ps/builtin-config-cleanup (2024-05-15) 22 commits
395
- - builtin/config: pass data between callbacks via local variables
396
- - builtin/config: convert flags to a local variable
397
- - builtin/config: track "fixed value" option via flags only
398
- - builtin/config: convert `key` to a local variable
399
- - builtin/config: convert `key_regexp` to a local variable
400
- - builtin/config: convert `regexp` to a local variable
401
- - builtin/config: convert `value_pattern` to a local variable
402
- - builtin/config: convert `do_not_match` to a local variable
403
- - builtin/config: move `respect_includes_opt` into location options
404
- - builtin/config: move default value into display options
405
- - builtin/config: move type options into display options
406
- - builtin/config: move display options into local variables
407
- - builtin/config: move location options into local variables
408
- - builtin/config: refactor functions to have common exit paths
409
- - config: make the config source const
410
- - builtin/config: check for writeability after source is set up
411
- - builtin/config: move actions into `cmd_config_actions()`
412
- - builtin/config: move legacy options into `cmd_config()`
413
- - builtin/config: move subcommand options into `cmd_config()`
414
- - builtin/config: move legacy mode into its own function
415
- - builtin/config: stop printing full usage on misuse
416
- - Merge branch 'ps/config-subcommands' into ps/builtin-config-cleanup
300
+ (merged to 'next' on 2024-05-20 at b6f728f1f5)
301
+ + builtin/config: pass data between callbacks via local variables
302
+ + builtin/config: convert flags to a local variable
303
+ + builtin/config: track "fixed value" option via flags only
304
+ + builtin/config: convert `key` to a local variable
305
+ + builtin/config: convert `key_regexp` to a local variable
306
+ + builtin/config: convert `regexp` to a local variable
307
+ + builtin/config: convert `value_pattern` to a local variable
308
+ + builtin/config: convert `do_not_match` to a local variable
309
+ + builtin/config: move `respect_includes_opt` into location options
310
+ + builtin/config: move default value into display options
311
+ + builtin/config: move type options into display options
312
+ + builtin/config: move display options into local variables
313
+ + builtin/config: move location options into local variables
314
+ + builtin/config: refactor functions to have common exit paths
315
+ + config: make the config source const
316
+ + builtin/config: check for writeability after source is set up
317
+ + builtin/config: move actions into `cmd_config_actions()`
318
+ + builtin/config: move legacy options into `cmd_config()`
319
+ + builtin/config: move subcommand options into `cmd_config()`
320
+ + builtin/config: move legacy mode into its own function
321
+ + builtin/config: stop printing full usage on misuse
322
+ + Merge branch 'ps/config-subcommands' into ps/builtin-config-cleanup
323
324
Code clean-up to reduce inter-function communication inside
325
builtin/config.c done via the use of global variables.
326
421
- Will merge to 'next'?
327
+ Will merge to 'master'.
328
source: <cover.1715755055.git.ps@pks.im>
329
330
331
* jc/doc-manpages-l10n (2024-05-17) 1 commit
426
- - SubmittingPatches: advertise git-manpages-l10n project a bit
332
+ (merged to 'next' on 2024-05-20 at fb103ed70f)
333
+ + SubmittingPatches: advertise git-manpages-l10n project a bit
334
335
The SubmittingPatches document now refers folks to manpages
336
translation project.
337
431
- Will merge to 'next'.
338
+ Will merge to 'master'.
339
source: <xmqqv83muc12.fsf@gitster.g>
340
341
@@ -460,7 +367,8 @@ Release tarballs are available at:
367
We forgot to normalize the result of getcwd() to NFC on macOS where
368
all other paths are normalized, which has been corrected.
369
463
- Will merge to 'master'.
370
+ On hold.
371
+ cf. <20240520160601.GA29154@tb-raspi4>
372
source: <20240509161110.12121-1-tboegi@web.de>
373
374
@@ -498,25 +406,6 @@ Release tarballs are available at:
406
source: <xmqqbk5i3ncw.fsf_-_@gitster.g>
407
408
501
-* kn/ref-transaction-symref (2024-05-07) 8 commits
502
- (merged to 'next' on 2024-05-11 at 0a7119f2a3)
503
- + refs: remove `create_symref` and associated dead code
504
- + refs: rename `refs_create_symref()` to `refs_update_symref()`
505
- + refs: use transaction in `refs_create_symref()`
506
- + refs: add support for transactional symref updates
507
- + refs: move `original_update_refname` to 'refs.c'
508
- + refs: support symrefs in 'reference-transaction' hook
509
- + files-backend: extract out `create_symref_lock()`
510
- + refs: accept symref values in `ref_transaction_update()`
511
- (this branch is used by kn/update-ref-symref.)
512
-
513
- Updates to symbolic refs can now be made as a part of ref
514
- transaction.
515
-
516
- Will merge to 'master'.
517
- source: <20240507125859.132116-1-knayak@gitlab.com>
518
-
519
-
409
* ps/reftable-write-options (2024-05-13) 11 commits
410
- refs/reftable: allow configuring geometric factor
411
- reftable: make the compaction factor configurable
@@ -538,21 +427,22 @@ Release tarballs are available at:
427
428
429
* ps/pseudo-ref-terminology (2024-05-15) 10 commits
541
- - refs: refuse to write pseudorefs
542
- - ref-filter: properly distinuish pseudo and root refs
543
- - refs: pseudorefs are no refs
544
- - refs: classify HEAD as a root ref
545
- - refs: do not check ref existence in `is_root_ref()`
546
- - refs: rename `is_special_ref()` to `is_pseudo_ref()`
547
- - refs: rename `is_pseudoref()` to `is_root_ref()`
548
- - Documentation/glossary: define root refs as refs
549
- - Documentation/glossary: clarify limitations of pseudorefs
550
- - Documentation/glossary: redefine pseudorefs as special refs
430
+ (merged to 'next' on 2024-05-20 at fc0f1f2607)
431
+ + refs: refuse to write pseudorefs
432
+ + ref-filter: properly distinuish pseudo and root refs
433
+ + refs: pseudorefs are no refs
434
+ + refs: classify HEAD as a root ref
435
+ + refs: do not check ref existence in `is_root_ref()`
436
+ + refs: rename `is_special_ref()` to `is_pseudo_ref()`
437
+ + refs: rename `is_pseudoref()` to `is_root_ref()`
438
+ + Documentation/glossary: define root refs as refs
439
+ + Documentation/glossary: clarify limitations of pseudorefs
440
+ + Documentation/glossary: redefine pseudorefs as special refs
441
442
Terminology to call various ref-like things are getting
443
straightened out.
444
555
- Will merge to 'next'?
445
+ Will merge to 'master'.
446
cf. <vgzwb5xnlvz2gfiqamzrfcjs2xya3zhhoootyzopfpdrjapayq@wfsomyal4cf6>
447
source: <cover.1715755591.git.ps@pks.im>
448
@@ -590,7 +480,7 @@ Release tarballs are available at:
480
this will smoke out codepaths that rely on such an unwarranted
481
assumptions.
482
593
- Will cook in 'next'.
483
+ Will cook in 'next', as it has known breakage.
484
source: <cover.1715057362.git.ps@pks.im>
485
486
@@ -608,11 +498,12 @@ Release tarballs are available at:
498
499
500
* ds/send-email-per-message-block (2024-04-10) 1 commit
611
- - send-email: move newline characters out of a few translatable strings
501
+ (merged to 'next' on 2024-05-20 at 189c49a1ca)
502
+ + send-email: move newline characters out of a few translatable strings
503
504
Preliminary code clean-up for "git send-email".
505
615
- Will merge to 'next'.
506
+ Will merge to 'master'.
507
The topmost commit in the original series was dropped per author's request.
508
cf. <a07d3807a24f6d68cb48ee48366ae25e@manjaro.org>
509
source: <29ea3a9b07bf1aa17b5d6a1e41325379c494bcb2.1712732383.git.dsimic@manjaro.org>