What's cooking (2024/04 #10)
Junio C Hamano committed
Apr 29, 2024 at 09:31 UTC
4eac2bdcb6777711d0dcf887e061a33c755c1fc8
1 file changed
+101
-210
whats-cooking.txt
+101
-210
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Apr 2024, #09; Tue, 23)
3
-X-master-at: bf995e7a4f94a9388aa8042dc9e338f3fcb75496
4
-X-next-at: d95f3e8691c1cba156beb6189d8229bc2ee0caab
2
+Subject: What's cooking in git.git (Apr 2024, #10; Mon, 29)
3
+X-master-at: 786a3e4b8d754d2b14b1208b98eeb0a554ef19a8
4
+X-next-at: b9fe23f5ca751025eab840f4e693bd4f1ac413cb
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Apr 2024, #09; Tue, 23)
7
+What's cooking in git.git (Apr 2024, #10; Mon, 29)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -17,7 +17,7 @@ topic without enough support may be discarded after a long period of
17
no activity (of course they can be resubmit when new interests
18
arise).
19
20
-A release candidate Git 2.45-rc1 has been tagged.
20
+Git 2.45 has been tagged.
21
22
Copies of the source code to Git live in many repositories, and the
23
following is a list of the ones I push into or their mirrors. Some
@@ -50,161 +50,65 @@ Release tarballs are available at:
50
--------------------------------------------------
51
[Graduated to 'master']
52
53
-* dd/t9604-use-posix-timezones (2024-04-10) 1 commit
54
- (merged to 'next' on 2024-04-16 at 46ab81737f)
55
- + t9604: Fix test for musl libc and new Debian
56
-
57
- The cvsimport tests required that the platform understands
58
- traditional timezone notations like CST6CDT, which has been
59
- updated to work on those systems as long as they understand
60
- POSIX notation with explicit tz transition dates.
61
- source: <20240410032812.30476-1-congdanhqx@gmail.com>
62
-
63
-
64
-* la/format-trailer-info (2024-03-15) 5 commits
65
- (merged to 'next' on 2024-04-16 at dca4784407)
66
- + trailer: finish formatting unification
67
- + trailer: begin formatting unification
68
- + format_trailer_info(): append newline for non-trailer lines
69
- + format_trailer_info(): drop redundant unfold_value()
70
- + format_trailer_info(): use trailer_item objects
71
- (this branch is used by la/hide-trailer-info.)
72
-
73
- The code to format trailers have been cleaned up.
74
- source: <pull.1694.git.1710485706.gitgitgadget@gmail.com>
75
-
76
-
77
-* mr/rerere-crash-fix (2024-04-16) 1 commit
78
- (merged to 'next' on 2024-04-17 at 60be8e2d74)
79
- + rerere: fix crashes due to unmatched opening conflict markers
80
-
81
- When .git/rr-cache/ rerere database gets corrupted or rerere is fed to
82
- work on a file with conflicted hunks resolved incompletely, the rerere
83
- machinery got confused and segfaulted, which has been corrected.
84
- source: <20240416105320.1113401-1-marcel@roethke.info>
85
-
86
-
87
-* pk/bisect-use-show (2024-04-15) 1 commit
88
- (merged to 'next' on 2024-04-22 at 4dd13c288f)
89
- + bisect: report the found commit with "show"
90
-
91
- When "git bisect" reports the commit it determined to be the
92
- culprit, we used to show it in a format that does not honor common
93
- UI tweaks, like log.date and log.decorate. The code has been
94
- taught to use "git show" to follow more customizations.
95
- source: <965ae345-fd58-c46c-5a7a-de181e901f21@softwolves.pp.se>
96
-
97
-
98
-* ps/missing-btmp-fix (2024-04-15) 1 commit
99
- (merged to 'next' on 2024-04-16 at c70779ba4b)
100
- + pack-bitmap: gracefully handle missing BTMP chunks
101
-
102
- GIt 2.44 introduced a regression that makes the updated code to
103
- barf in repositories with multi-pack index written by older
104
- versions of Git, which has been corrected.
105
- source: <a8251f8278ba9a3b41a8e299cb4918a62df6d1c7.1713163238.git.ps@pks.im>
106
-
107
-
108
-* ps/reftable-block-iteration-optim (2024-04-15) 10 commits
109
- (merged to 'next' on 2024-04-15 at 3a2353c7f2)
110
- + reftable/block: avoid copying block iterators on seek
111
- + reftable/block: reuse `zstream` state on inflation
112
- + reftable/block: open-code call to `uncompress2()`
113
- + reftable/block: reuse uncompressed blocks
114
- + reftable/reader: iterate to next block in place
115
- + reftable/block: move ownership of block reader into `struct table_iter`
116
- + reftable/block: introduce `block_reader_release()`
117
- + reftable/block: better grouping of functions
118
- + reftable/block: merge `block_iter_seek()` and `block_reader_seek()`
119
- + reftable/block: rename `block_reader_start()`
120
-
121
- The code to iterate over reftable blocks has seen some optimization
122
- to reduce memory allocation and deallocation.
123
- source: <cover.1712578376.git.ps@pks.im>
124
-
125
-
126
-* ps/run-auto-maintenance-in-receive-pack (2024-04-17) 2 commits
127
- (merged to 'next' on 2024-04-22 at cacdcac452)
128
- + builtin/receive-pack: convert to use git-maintenance(1)
129
- + run-command: introduce function to prepare auto-maintenance process
130
-
131
- The "receive-pack" program (which responds to "git push") was not
132
- converted to run "git maintenance --auto" when other codepaths that
133
- used to run "git gc --auto" were updated, which has been corrected.
134
- source: <cover.1713334241.git.ps@pks.im>
135
-
136
-
137
-* rj/launch-editor-error-message (2024-04-15) 1 commit
138
- (merged to 'next' on 2024-04-16 at 3d0dd46fc2)
139
- + launch_editor: waiting message on error
140
-
141
- Git writes a "waiting for your editor" message on an incomplete
142
- line after launching an editor, and then append another error
143
- message on the same line if the editor errors out. It now clears
144
- the "waiting for..." line before giving the error message.
145
- source: <e208da74-8f16-44ae-912e-ae968da82057@gmail.com>
146
-
53
+* rj/add-i-leak-fix (2024-04-22) 4 commits
54
+ (merged to 'next' on 2024-04-23 at b10e350a54)
55
+ + add: plug a leak on interactive_add
56
+ + add-patch: plug a leak handling the '/' command
57
+ + add-interactive: plug a leak in get_untracked_files
58
+ + apply: plug a leak in apply_data
59
148
-* rs/apply-reject-long-name (2024-04-16) 1 commit
149
- (merged to 'next' on 2024-04-17 at 701ccded8b)
150
- + apply: avoid using fixed-size buffer in write_out_one_reject()
60
+ Leakfix.
61
+ source: <69f86760-96ff-4c62-9649-4627652b7c19@gmail.com>
62
152
- The filename used for rejected hunks "git apply --reject" creates
153
- was limited to PATH_MAX, which has been lifted.
154
- source: <a93cd243-cb17-4ad5-8d23-30768dc5213b@web.de>
63
64
+* rs/vsnprintf-failure-is-not-a-bug (2024-04-21) 1 commit
65
+ (merged to 'next' on 2024-04-23 at bf66ab6ea7)
66
+ + don't report vsnprintf(3) error as bug
67
157
-* rs/imap-send-simplify-cmd-issuing-codepath (2024-04-15) 1 commit
158
- (merged to 'next' on 2024-04-17 at 0255e49f8b)
159
- + imap-send: increase command size limit
68
+ Demote a BUG() to an die() when the failure from vsnprintf() may
69
+ not be due to a programmer error.
70
+ source: <ea752a2b-9b74-4a59-a037-4782abf7161e@web.de>
71
161
- Code simplification.
162
- source: <7026075c-db4e-4d43-bbd1-d2edb52da9b7@web.de>
72
+--------------------------------------------------
73
+[New Topics]
74
75
+* rh/complete-symbolic-ref (2024-04-25) 3 commits
76
+ - completion: add docs on how to add subcommand completions
77
+ - completion: improve docs for using __git_complete
78
+ - completion: add 'symbolic-ref'
79
165
-* rs/no-openssl-compilation-fix-on-macos (2024-04-15) 1 commit
166
- (merged to 'next' on 2024-04-15 at 48cab93d0a)
167
- + git-compat-util: fix NO_OPENSSL on current macOS
80
+ Command line completion script (in contrib/) learned to complete
81
+ "git symbolic-ref" a bit better (you need to enable plumbing
82
+ commands to be completed with GIT_COMPLETION_SHOW_ALL_COMMANDS).
83
169
- Build fix.
170
- source: <3188f4e2-9744-40b1-8f05-0896b8679d25@web.de>
84
+ Will merge to 'next'.
85
+ source: <20240425101845.708554-3-rhi@pengutronix.de>
86
87
173
-* ta/fast-import-parse-path-fix (2024-04-15) 8 commits
174
- (merged to 'next' on 2024-04-15 at 00cc71a679)
175
- + fast-import: make comments more precise
176
- + fast-import: forbid escaped NUL in paths
177
- + fast-import: document C-style escapes for paths
178
- + fast-import: improve documentation for path quoting
179
- + fast-import: remove dead strbuf
180
- + fast-import: allow unquoted empty path for root
181
- + fast-import: directly use strbufs for paths
182
- + fast-import: tighten path unquoting
88
+* jt/doc-submitting-rerolled-series (2024-04-25) 1 commit
89
+ - doc: clarify practices for submitting updated patch versions
90
184
- The way "git fast-import" handles paths described in its input has
185
- been tightened up and more clearly documented.
186
- source: <cover.1713056559.git.thalia@archibald.dev>
91
+ Developer doc update.
92
93
+ Will merge to 'next'.
94
+ source: <20240425213404.133660-1-jltobler@gmail.com>
95
189
-* xx/rfc2822-date-format-in-doc (2024-04-12) 1 commit
190
- (merged to 'next' on 2024-04-17 at f2186bd6e8)
191
- + Documentation: fix typos describing date format
96
193
- Docfix.
194
- source: <pull.1716.git.1712911876943.gitgitgadget@gmail.com>
97
+* bc/zsh-compatibility (2024-04-26) 2 commits
98
+ - vimdiff: make script and tests work with zsh
99
+ - t4046: avoid continue in &&-chain for zsh
100
101
+ source: <20240426221154.2194139-1-sandals@crustytoothpaste.net>
102
197
-* yb/replay-doc-linkfix (2024-04-15) 1 commit
198
- (merged to 'next' on 2024-04-15 at e8cf9cd9a8)
199
- + Documentation: fix linkgit reference
103
201
- Docfix.
202
- source: <pull.1706.git.git.1713132482976.gitgitgadget@gmail.com>
104
+* jc/rev-parse-fatal-doc (2024-04-28) 1 commit
105
+ - rev-parse: document that most of the time you need to be in a repository
106
107
--------------------------------------------------
205
-[New Topics]
108
+[Cooking]
109
207
-* ps/undecided-is-not-necessarily-sha1 (2024-04-23) 12 commits
110
+* ps/undecided-is-not-necessarily-sha1 (2024-04-29) 13 commits
111
+ - SQUASH???
112
- repository: stop setting SHA1 as the default object hash
113
- builtin/shortlog: don't set up revisions without repo
114
- builtin/diff: explicitly set hash algo when there is no repo
@@ -223,11 +127,10 @@ Release tarballs are available at:
127
this will smoke out codepaths that rely on such an unwarranted
128
assumptions.
129
226
- Will merge to 'next'?
130
+ fuzz-smoke-test job at GitHub Actions CI breaks with this in 'seen'
131
+ cf. <xmqqwmoi31aw.fsf@gitster.g>
132
source: <cover.1713848619.git.ps@pks.im>
133
229
---------------------------------------------------
230
-[Cooking]
134
135
* aj/stash-staged-fix (2024-04-22) 1 commit
136
(merged to 'next' on 2024-04-23 at d49e9dade0)
@@ -240,43 +143,19 @@ Release tarballs are available at:
143
source: <pull.1722.git.1713781694490.gitgitgadget@gmail.com>
144
145
243
-* rj/add-i-leak-fix (2024-04-22) 4 commits
244
- (merged to 'next' on 2024-04-23 at b10e350a54)
245
- + add: plug a leak on interactive_add
246
- + add-patch: plug a leak handling the '/' command
247
- + add-interactive: plug a leak in get_untracked_files
248
- + apply: plug a leak in apply_data
249
-
250
- Leakfix.
251
-
252
- Will merge to 'master'.
253
- source: <69f86760-96ff-4c62-9649-4627652b7c19@gmail.com>
254
-
255
-
256
-* rj/add-p-typo-reaction (2024-04-21) 1 commit
257
- (merged to 'next' on 2024-04-23 at 8ac0509b47)
258
- + add-patch: response to unknown command
146
+* rj/add-p-typo-reaction (2024-04-26) 1 commit
147
+ - add-patch: response to unknown command
148
149
When the user responds to a prompt given by "git add -p" with an
150
unsupported command, list of available commands were given, which
151
was too much if the user knew what they wanted to type but merely
152
made a typo. Now the user gets a much shorter error message.
153
265
- Will cook in 'next'.
154
+ Expecting a reroll.
155
+ cf. <305296f1-975b-41b9-968c-3984d8056196@gmail.com>
156
source: <b209a2b8-f98f-4f14-a687-9022d30968dd@gmail.com>
157
158
269
-* rs/vsnprintf-failure-is-not-a-bug (2024-04-21) 1 commit
270
- (merged to 'next' on 2024-04-23 at bf66ab6ea7)
271
- + don't report vsnprintf(3) error as bug
272
-
273
- Demote a BUG() to an die() when the failure from vsnprintf() may
274
- not be due to a programmer error.
275
-
276
- Will merge to 'master'.
277
- source: <ea752a2b-9b74-4a59-a037-4782abf7161e@web.de>
278
-
279
-
159
* ds/format-patch-rfc-and-k (2024-04-19) 1 commit
160
(merged to 'next' on 2024-04-23 at b3b0c5507a)
161
+ format-patch: ensure that --rfc and -k are mutually exclusive
@@ -315,7 +194,7 @@ Release tarballs are available at:
194
by always instantiating "the_repository" and replacing references
195
to "the_index" with references to its .index member.
196
318
- Comments?
197
+ Will merge to 'next'?
198
source: <cover.1713442061.git.ps@pks.im>
199
200
@@ -336,18 +215,17 @@ Release tarballs are available at:
215
source: <cover.1713445918.git.phillip.wood@dunelm.org.uk>
216
217
339
-* js/for-each-repo-keep-going (2024-04-18) 2 commits
340
- - maintenance: running maintenance should not stop on errors
341
- - for-each-repo: optionally keep going on an error
218
+* js/for-each-repo-keep-going (2024-04-24) 2 commits
219
+ (merged to 'next' on 2024-04-25 at d33253d919)
220
+ + maintenance: running maintenance should not stop on errors
221
+ + for-each-repo: optionally keep going on an error
222
223
A scheduled "git maintenance" job is expected to work on all
224
repositories it knows about, but it stopped at the first one that
225
errored out. Now it keeps going.
226
347
- Expecting a hopefully small and final reroll.
348
- Can change exit condition, which needs fixing.
349
- cf. <20240419175621.GB14309@coredump.intra.peff.net>
350
- source: <pull.1719.v2.git.1713444783.gitgitgadget@gmail.com>
227
+ Will cook in 'next'.
228
+ source: <pull.1719.v3.git.1713975299.gitgitgadget@gmail.com>
229
230
231
* xx/disable-replace-when-building-midx (2024-04-17) 1 commit
@@ -362,34 +240,38 @@ Release tarballs are available at:
240
source: <pull.1711.v2.git.1712554017808.gitgitgadget@gmail.com>
241
242
365
-* kn/update-ref-symrefs (2024-04-12) 8 commits
366
- - SQUASH???
367
- - refs: support symrefs in 'reference-transaction' hook
368
- - update-ref: add support for symref-update
369
- - update-ref: add support for symref-create
243
+* kn/update-ref-symrefs (2024-04-26) 7 commits
244
+ - ref: support symrefs in 'reference-transaction' hook
245
+ - update-ref: add support for 'symref-update' command
246
+ - update-ref: add support for 'symref-create' command
247
+ - update-ref: add support for 'symref-delete' command
248
+ - update-ref: add support for 'symref-verify' command
249
- files-backend: extract out `create_symref_lock`
371
- - update-ref: add support for symref-delete
372
- - update-ref: add support for symref-verify
250
- refs: accept symref values in `ref_transaction[_add]_update`
251
375
- source: <20240412095908.1134387-1-knayak@gitlab.com>
252
+ "update-ref" learns to also handle symbolic refs.
253
+
254
+ Expecting a reroll.
255
+ cf. <CAOLa=ZT4yVEuZXmiTVB2tf0qaTPCPn=0TcJRc89knZQWZBbFTg@mail.gmail.com>
256
+ source: <20240426152449.228860-1-knayak@gitlab.com>
257
258
259
* la/doc-use-of-contacts-when-contributing (2024-04-18) 8 commits
379
- - SubmittingPatches: demonstrate using git-contacts with git-send-email
380
- - SubmittingPatches: add heading for format-patch and send-email
381
- - SubmittingPatches: dedupe discussion of security patches
382
- - SubmittingPatches: discuss reviewers first
383
- - SubmittingPatches: quote commands
384
- - SubmittingPatches: mention GitGitGadget
385
- - SubmittingPatches: clarify 'git-contacts' location
386
- - MyFirstContribution: mention contrib/contacts/git-contacts
260
+ (merged to 'next' on 2024-04-25 at 5102a45f63)
261
+ + SubmittingPatches: demonstrate using git-contacts with git-send-email
262
+ + SubmittingPatches: add heading for format-patch and send-email
263
+ + SubmittingPatches: dedupe discussion of security patches
264
+ + SubmittingPatches: discuss reviewers first
265
+ + SubmittingPatches: quote commands
266
+ + SubmittingPatches: mention GitGitGadget
267
+ + SubmittingPatches: clarify 'git-contacts' location
268
+ + MyFirstContribution: mention contrib/contacts/git-contacts
269
270
Advertise "git contacts", a tool for newcomers to find people to
271
ask review for their patches, a bit more in our developer
272
documentation.
273
392
- Will merge to 'next'.
274
+ Will cook in 'next'.
275
source: <pull.1704.v6.git.1713477125.gitgitgadget@gmail.com>
276
277
@@ -410,6 +292,8 @@ Release tarballs are available at:
292
293
Tests to ensure interoperability between reftable written by jgit
294
and our code have been added and enabled in CI.
295
+
296
+ Will merge to 'next'.
297
source: <cover.1712896868.git.ps@pks.im>
298
299
@@ -441,6 +325,8 @@ Release tarballs are available at:
325
326
Code to write out reftable has seen some optimization and
327
simplification.
328
+
329
+ Will merge to 'next'?
330
source: <cover.1712578837.git.ps@pks.im>
331
332
@@ -451,7 +337,7 @@ Release tarballs are available at:
337
"git send-email" learned to separate its reports on each message it
338
sends out with an extra blank line in between.
339
454
- Comments?
340
+ Will merge to 'next'?
341
source: <cover.1712732383.git.dsimic@manjaro.org>
342
343
@@ -489,6 +375,8 @@ Release tarballs are available at:
375
The credential helper protocol, together with the HTTP layer, have
376
been enhanced to support authentication schemes different from
377
username & password pair, like Bearer and NTLM.
378
+
379
+ Comments?
380
source: <20240417000240.3611948-1-sandals@crustytoothpaste.net>
381
382
@@ -528,7 +416,9 @@ Release tarballs are available at:
416
source: <cover.1710972293.git.me@ttaylorr.com>
417
418
531
-* la/hide-trailer-info (2024-04-19) 9 commits
419
+* la/hide-trailer-info (2024-04-26) 11 commits
420
+ - trailer unit tests: inspect iterator contents
421
+ - trailer: document parse_trailers() usage
422
- trailer: retire trailer_info_get() from API
423
- trailer: make trailer_info struct private
424
- trailer: make parse_trailers() return trailer_info pointer
@@ -537,12 +427,13 @@ Release tarballs are available at:
427
- trailer: teach iterator about non-trailer lines
428
- trailer: add unit tests for trailer iterator
429
- Makefile: sort UNIT_TEST_PROGRAMS
540
- - Merge branch 'la/format-trailer-info' into la/hide-trailer-info
430
+ + Merge branch 'la/format-trailer-info' into la/hide-trailer-info
431
432
The trailer API has been reshuffled a bit.
433
544
- Will merge to 'next'.
545
- source: <pull.1696.v2.git.1713504153.gitgitgadget@gmail.com>
434
+ Will merge to 'next'?
435
+ cf. <CAP8UFD0ZHpo7US6dx_WK6F_1JYsBdHunBaW86qM1CzOKaPC-aA@mail.gmail.com>
436
+ source: <pull.1696.v3.git.1714091170.gitgitgadget@gmail.com>
437
438
439
* ds/doc-config-reflow (2024-03-14) 1 commit
@@ -568,17 +459,16 @@ Release tarballs are available at:
459
source: <20240319183722.211300-1-ignacio@iencinas.com>
460
461
571
-* js/build-fuzz-more-often (2024-04-11) 2 commits
572
- - fuzz: link fuzz programs with `make all` on Linux
573
- - ci: also define CXX environment variable
462
+* js/build-fuzz-more-often (2024-04-24) 1 commit
463
+ (merged to 'next' on 2024-04-25 at 28f65d1be2)
464
+ + fuzz: link fuzz programs with `make all` on Linux
465
466
In addition to building the objects needed, try to link the objects
467
that are used in fuzzer tests, to make sure at least they build
468
without bitrot, in Linux CI runs.
469
579
- Expecting a hopefully small and final reroll.
580
- cf. <20240412042247.GA1077925@coredump.intra.peff.net>
581
- source: <cover.1712858920.git.steadmon@google.com>
470
+ Will cook in 'next'.
471
+ source: <ba9d24c6445de309226bf7c165499f1969807fef.1713982389.git.steadmon@google.com>
472
473
474
* cw/git-std-lib (2024-02-28) 4 commits
@@ -593,7 +483,7 @@ Release tarballs are available at:
483
source: <cover.1696021277.git.jonathantanmy@google.com>
484
485
596
-* js/cmake-with-test-tool (2024-02-23) 2 commits
486
+* js/cmake-with-test-tool (2024-04-24) 2 commits
487
- cmake: let `test-tool` run the unit tests, too
488
- Merge branch 'js/unit-test-suite-runner' into js/cmake-with-test-tool
489
(this branch uses js/unit-test-suite-runner.)
@@ -601,10 +491,11 @@ Release tarballs are available at:
491
"test-tool" is now built in CMake build to also run the unit tests.
492
493
May want to roll it into the base topic.
494
+ Will merge to 'next' together with the base topic.
495
source: <pull.1666.git.1708038924522.gitgitgadget@gmail.com>
496
497
607
-* js/unit-test-suite-runner (2024-02-23) 8 commits
498
+* js/unit-test-suite-runner (2024-04-24) 8 commits
499
- ci: use test-tool as unit test runner on Windows
500
- t/Makefile: run unit tests alongside shell tests
501
- unit tests: add rule for running with test-tool
@@ -619,7 +510,7 @@ Release tarballs are available at:
510
bypassing the need to use the "prove" tool.
511
512
Needs review.
622
- source: <cover.1708728717.git.steadmon@google.com>
513
+ source: <cover.1713985716.git.steadmon@google.com>
514
515
516
* bk/complete-dirname-for-am-and-format-patch (2024-01-12) 1 commit