What's cooking (2025/09 #09)
Junio C Hamano committed
Sep 22, 2025 at 15:42 UTC
8e7d1eac65a35589dd4c2a73f8511b9a9ffd490f
1 file changed
+101
-163
whats-cooking.txt
+101
-163
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Sep 2025, #08; Fri, 19)
2
+Subject: What's cooking in git.git (Sep 2025, #09; Mon, 22)
3
X-master-at: ca2559c1d630eb4f04cdee2328aaf1c768907a9e
4
-X-next-at: c4e3cb95175ecb4a955ccff0899fd16de0cea8e8
4
+X-next-at: b178f27e6ddfa8d515dcd445b6bf17119f962c44
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Sep 2025, #08; Fri, 19)
7
+What's cooking in git.git (Sep 2025, #09; Mon, 22)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -46,111 +46,75 @@ Release tarballs are available at:
46
https://www.kernel.org/pub/software/scm/git/
47
48
--------------------------------------------------
49
-[Graduated to 'master']
50
-
51
-* ag/doc-sendmail-gmail-example-update (2025-08-26) 1 commit
52
- (merged to 'next' on 2025-09-12 at 54e0dab4b0)
53
- + docs: update sendmail docs to use more secure SMTP server for Gmail
54
-
55
- Doc update.
56
- source: <20250826150919.5239-1-gargaditya08@live.com>
57
-
58
-
59
-* ag/send-email-imap-sent (2025-08-11) 2 commits
60
- (merged to 'next' on 2025-09-12 at bb82691e0a)
61
- + send-email: enable copying emails to an IMAP folder without actually sending them
62
- + send-email: add ability to send a copy of sent emails to an IMAP folder
63
-
64
- "git send-email" learned to drive "git imap-send" to store already
65
- sent e-mails in an IMAP folder.
66
- source: <PN3PR01MB9597E8E33868386C997D2563B82BA@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM>
67
-
68
-
69
-* jc/doc-includeif-hasconfig-remote-url-fix (2025-08-21) 1 commit
70
- (merged to 'next' on 2025-09-12 at 3b91910cbd)
71
- + config: document includeIf conditions consistently
72
-
73
- Doc mark-up fix.
74
- source: <xmqqldnc4stv.fsf@gitster.g>
75
-
76
-
77
-* jc/longer-disambiguation-fix (2025-08-14) 1 commit
78
- (merged to 'next' on 2025-09-12 at 4dddaa05fc)
79
- + abbrev: allow extending beyond 32 chars to disambiguate
80
-
81
- "git rev-parse --short" and friends failed to disambiguate two
82
- objects with object names that share common prefix longer than 32
83
- characters, which has been fixed.
84
- source: <xmqqh5ya6iua.fsf_-_@gitster.g>
85
-
86
-
87
-* jk/curl-global-trace-components (2025-08-27) 1 commit
88
- (merged to 'next' on 2025-09-12 at 37a826f245)
89
- + curl: add support for curl_global_trace() components
90
-
91
- Adjust to the way newer versions of cURL selectivel enables tracing
92
- options, so that our tests can continue to work.
93
- source: <20250827080702.GA3572995@coredump.intra.peff.net>
94
-
95
-
96
-* kh/doc-fast-import-markup-fix (2025-09-08) 1 commit
97
- (merged to 'next' on 2025-09-12 at d56e1334b9)
98
- + doc: fast-import: replace literal block with paragraph
99
-
100
- Doc mark-up fix.
101
- source: <09aaad696895c18c6d4dda7d6a2f4b77f84f39ba.1757363213.git.code@khaugsbakk.name>
49
+[New Topics]
50
51
+* jk/setup-revisions-freefix (2025-09-19) 6 commits
52
+ (merged to 'next' on 2025-09-22 at b178f27e6d)
53
+ + revision: retain argv NULL invariant in setup_revisions()
54
+ + treewide: pass strvecs around for setup_revisions_from_strvec()
55
+ + treewide: use setup_revisions_from_strvec() when we have a strvec
56
+ + revision: add wrapper to setup_revisions() from a strvec
57
+ + revision: manage memory ownership of argv in setup_revisions()
58
+ + stash: tell setup_revisions() to free our allocated strings
59
104
-* kn/clang-format-bitfields (2025-08-26) 1 commit
105
- (merged to 'next' on 2025-09-12 at 62dd6102f6)
106
- + Documentation: note styling for bit fields
60
+ There are double frees and leaks around setup_revisions() API used
61
+ in "git stash show", which has been fixed, and setup_revisions()
62
+ API gained a wrapper to make it more ergonomic when using it with
63
+ strvec-manged argc/argv pairs.
64
108
- CodingGuidelines now spells out how bitfields are to be written.
109
- source: <20250826121928.22317-1-karthik.188@gmail.com>
65
+ Expecting a reroll to fix t3903
66
+ cf. <xmqq1pnywkwv.fsf@gitster.g>
67
+ source: <20250919223351.GA3906184@coredump.intra.peff.net>
68
69
112
-* ne/alloc-free-and-null (2025-09-04) 1 commit
113
- (merged to 'next' on 2025-09-12 at 005f763f97)
114
- + alloc: fix dangling pointer in alloc_state cleanup
70
+* js/curl-off-t-fixes (2025-09-21) 3 commits
71
+ - http-push: avoid new compile error
72
+ - imap-send: be more careful when casting to `curl_off_t`
73
+ - http: offer to cast `size_t` to `curl_off_t` safely
74
116
- The clear_alloc_state() API function was not fully clearing the
117
- structure for reuse, but since nobody reuses it, replace it with a
118
- variant that frees the structure as well, making the callers simpler.
119
- source: <pull.2040.v5.git.git.1757007856062.gitgitgadget@gmail.com>
75
+ A few places where an size_t value was cast to curl_off_t without
76
+ checking has been updated to use the existing helper function.
77
78
+ Expecting a (hopefully small) reroll to clarify log message.
79
+ cf. <pull.1974.git.1758457356.gitgitgadget@gmail.com>
80
+ source: <pull.1974.git.1758457356.gitgitgadget@gmail.com>
81
122
-* pc/range-diff-memory-limit (2025-08-29) 1 commit
123
- (merged to 'next' on 2025-09-12 at 022fe71829)
124
- + range-diff: add configurable memory limit for cost matrix
82
+--------------------------------------------------
83
+[Stalled]
84
126
- "git range-diff" learned a way to limit the memory consumed by
127
- O(N*N) cost matrix.
128
- source: <pull.1958.v4.git.1756483374980.gitgitgadget@gmail.com>
85
+These topics have been expecting updates for quite some time. I'll
86
+eject any of them when they start to conflict with other topics in
87
+'seen' and may drop them from my tree when they are dormant for too
88
+long (let's say 8 weeks is way too long, for now). After that, they
89
+can be proposed again by rerolling them in a shape that would work
90
+well with other topics in 'seen' (and of course 'next' and
91
+"master').
92
93
+* lc/rebase-trailer (2025-08-03) 2 commits
94
+ - rebase: support --trailer
95
+ - trailer: append trailers in-process and drop the fork to `interpret-trailers`
96
131
-* pw/3.0-commentchar-auto-deprecation (2025-08-26) 4 commits
132
- (merged to 'next' on 2025-09-12 at e6a855d738)
133
- + commit: print advice when core.commentString=auto
134
- + config: warn on core.commentString=auto
135
- + breaking-changes: deprecate support for core.commentString=auto
136
- + Merge branch 'ps/config-wo-the-repository' into pw/3.0-commentchar-auto-deprecation
97
+ Expecting a reroll.
98
+ cf. <198826af571.62b85cb31711042.2415806544948206668@linux.beauty>
99
+ cf. <xmqqiki7qasu.fsf@gitster.g>
100
+ source: <20250803150059.402017-1-me@linux.beauty>
101
138
- "core.commentChar=auto" that attempts to dynamically pick a
139
- suitable comment character is non-workable, as it is too much
140
- trouble to support for little benefit, and is marked as deprecated.
141
- source: <cover.1756215326.git.phillip.wood@dunelm.org.uk>
102
103
+* ac/deglobal-sparse-variables (2025-07-18) 3 commits
104
+ . environment: remove the global variable 'sparse_expect_files_outside_of_patterns'
105
+ . environment: move access to "core.sparsecheckoutcone" into repo_settings
106
+ . environment: move access to "core.sparsecheckout" into repo_settings
107
144
-* sg/line-log-boundary-fixes (2025-08-18) 2 commits
145
- (merged to 'next' on 2025-09-12 at 0d34d3872c)
146
- + line-log: show all line ranges touched by the same diff range
147
- + line-log: fix assertion error
108
+ Two global variables related to sparse checkout have been moved to
109
+ the repository settings structure.
110
149
- A corner case bug in "git log -L..." has been corrected.
150
- source: <20250818111310.1283932-1-szeder.dev@gmail.com>
111
+ Expecting a reroll.
112
+ cf. <CAE7as+bnG6KgA8X_n36pqP15bmyM6re+xEb1MOXKvZSUdJ8Arg@mail.gmail.com>
113
+ Ejected out of 'seen' for now.
114
+ source: <cover.1752882401.git.ayu.chandekar@gmail.com>
115
116
--------------------------------------------------
153
-[New Topics]
117
+[Cooking]
118
119
* kn/reftable-consistency-checks (2025-09-18) 9 commits
120
- fixup! reftable: check for trailing newline in 'tables.list'
@@ -171,14 +135,15 @@ Release tarballs are available at:
135
136
137
* pw/rebase-i-cleanup-fix (2025-09-18) 2 commits
174
- - sequencer: remove VERBATIM_MSG flag
175
- - rebase -i: respect commit.cleanup when picking fixups
138
+ (merged to 'next' on 2025-09-22 at 2d0aec7821)
139
+ + sequencer: remove VERBATIM_MSG flag
140
+ + rebase -i: respect commit.cleanup when picking fixups
141
142
"git rebase -i" failed to clean-up the commit log message when the
143
command commits the final one in a chain of "fixup" commands, which
144
has been corrected.
145
181
- Will merge to 'next'.
146
+ Will merge to 'master'.
147
source: <cover.1758186038.git.phillip.wood@dunelm.org.uk>
148
149
@@ -188,7 +153,7 @@ Release tarballs are available at:
153
"git last-modified" operating in non-recursive mode used to trigger
154
a BUG(), which has been corrected.
155
191
- Will merge to 'next'?
156
+ Will merge to 'next'.
157
source: <20250918-toon-fix-last-modified-v3-1-0c3910e224f6@iotcl.com>
158
159
@@ -233,42 +198,6 @@ Release tarballs are available at:
198
Comments?
199
source: <20250919010911.649831-1-sandals@crustytoothpaste.net>
200
236
---------------------------------------------------
237
-[Stalled]
238
-
239
-These topics have been expecting updates for quite some time. I'll
240
-eject any of them when they start to conflict with other topics in
241
-'seen' and may drop them from my tree when they are dormant for too
242
-long (let's say 8 weeks is way too long, for now). After that, they
243
-can be proposed again by rerolling them in a shape that would work
244
-well with other topics in 'seen' (and of course 'next' and
245
-"master').
246
-
247
-* lc/rebase-trailer (2025-08-03) 2 commits
248
- - rebase: support --trailer
249
- - trailer: append trailers in-process and drop the fork to `interpret-trailers`
250
-
251
- Expecting a reroll.
252
- cf. <198826af571.62b85cb31711042.2415806544948206668@linux.beauty>
253
- cf. <xmqqiki7qasu.fsf@gitster.g>
254
- source: <20250803150059.402017-1-me@linux.beauty>
255
-
256
-
257
-* ac/deglobal-sparse-variables (2025-07-18) 3 commits
258
- . environment: remove the global variable 'sparse_expect_files_outside_of_patterns'
259
- . environment: move access to "core.sparsecheckoutcone" into repo_settings
260
- . environment: move access to "core.sparsecheckout" into repo_settings
261
-
262
- Two global variables related to sparse checkout have been moved to
263
- the repository settings structure.
264
-
265
- Expecting a reroll.
266
- cf. <CAE7as+bnG6KgA8X_n36pqP15bmyM6re+xEb1MOXKvZSUdJ8Arg@mail.gmail.com>
267
- Ejected out of 'seen' for now.
268
- source: <cover.1752882401.git.ayu.chandekar@gmail.com>
269
-
270
---------------------------------------------------
271
-[Cooking]
201
202
* pw/add-p-hunk-splitting-fix (2025-09-15) 2 commits
203
- add-patch: update hunk splitability after editing
@@ -278,22 +207,22 @@ well with other topics in 'seen' (and of course 'next' and
207
all the split pieces 'selected'; this has been changed to make them
208
all 'undecided'.
209
281
- Comments?
210
+ Anybody wants to weign in to tiebreak on the BreakingChanges issue?
211
+ cf. <xmqq4it2pep0.fsf@gitster.g>
212
source: <pull.1863.v2.git.1757950144.gitgitgadget@gmail.com>
213
214
285
-* dk/stash-apply-index (2025-09-15) 4 commits
215
+* dk/stash-apply-index (2025-09-21) 4 commits
216
- stash: honor stash.index in apply, pop modes
217
- stash: refactor private config globals
218
- t3905: remove unneeded blank line
219
- t3903: reduce dependencies on previous tests
220
291
- The stash.index configuration variable canbe set to make "git stash
221
+ The stash.index configuration variable can be set to make "git stash
222
pop/apply" pretend that it was invoked with "--index".
223
294
- Expecting a (hopefully small and final) reroll.
295
- cf. <CALnO6CByUNHWFRYBSOpP-uD8moBrm48UW7k0MaGTUtL=bDL6GQ@mail.gmail.com>
296
- source: <cover.1757982870.git.ben.knoble+github@gmail.com>
224
+ Will merge to 'next'.
225
+ source: <cover.1758505011.git.ben.knoble+github@gmail.com>
226
227
228
* jk/color-variable-fixes (2025-09-16) 13 commits
@@ -318,7 +247,7 @@ well with other topics in 'seen' (and of course 'next' and
247
while the code has been cleaned up to prevent similar bugs in the
248
future.
249
321
- Will merge to 'next'?
250
+ Will merge to 'next'.
251
source: <20250916201036.GA612463@coredump.intra.peff.net>
252
source: <20250916202408.GI612873@coredump.intra.peff.net>
253
@@ -339,18 +268,19 @@ well with other topics in 'seen' (and of course 'next' and
268
A lot of code clean-up of xdiff.
269
Split out of a larger topic.
270
342
- Comments?
271
+ Will merge to 'next'.
272
source: <pull.2048.v3.git.git.1758294992.gitgitgadget@gmail.com>
273
274
275
* jc/3.0-default-initial-branch-to-main-addendum (2025-09-17) 1 commit
347
- - initial branch: give hints after switching the default name
276
+ (merged to 'next' on 2025-09-22 at dc4168c337)
277
+ + initial branch: give hints after switching the default name
278
(this branch uses pw/3.0-default-initial-branch-to-main.)
279
280
Keep giving hint about the default initial branch name for users
281
who may be surprised after Git 3.0 switchover.
282
353
- Will merge to 'next'.
283
+ Will merge to 'master'.
284
source: <cover.1757518141.git.phillip.wood@dunelm.org.uk>
285
286
@@ -382,7 +312,8 @@ well with other topics in 'seen' (and of course 'next' and
312
each other by encoding submodule names before using them as path
313
components.
314
385
- Comments?
315
+ Expecting a reroll.
316
+ cf. <87ecsf7g84.fsf@collabora.com> etc.
317
source: <20250908140117.262205-1-adrian.ratiu@collabora.com>
318
319
@@ -409,6 +340,8 @@ well with other topics in 'seen' (and of course 'next' and
340
- doc: git-push: create PUSH RULES section
341
342
Doc updates.
343
+
344
+ Will merge to 'next'.
345
source: <pull.1973.git.1758144815.gitgitgadget@gmail.com>
346
347
@@ -433,7 +366,9 @@ well with other topics in 'seen' (and of course 'next' and
366
source: <20250910031124.1807856-1-ask+git@howdoi.land>
367
368
436
-* ps/clar-updates (2025-09-10) 1 commit
369
+* ps/clar-updates (2025-09-22) 2 commits
370
+ (merged to 'next' on 2025-09-22 at c811e8c172)
371
+ + t/unit-tests: update to 10e96bc
372
(merged to 'next' on 2025-09-15 at 73402f7652)
373
+ t/unit-tests: update clar to fcbed04
374
@@ -441,9 +376,10 @@ well with other topics in 'seen' (and of course 'next' and
376
377
Will merge to 'master'.
378
source: <20250910-b4-pks-clar-update-v1-1-26a196237e0a@pks.im>
379
+ source: <20250922-pks-clar-update-v1-1-9154e7d1b7a1@pks.im>
380
381
446
-* ps/config-get-color-fixes (2025-09-17) 5 commits
382
+* ps/config-get-color-fixes (2025-09-22) 5 commits
383
- builtin/config: do not spawn pager when printing color codes
384
- builtin/config: special-case retrieving colors without a key
385
- builtin/config: do not die in `get_color()`
@@ -454,8 +390,8 @@ well with other topics in 'seen' (and of course 'next' and
390
sequence is for a particular type, e.g., "git config get
391
--type=color --default=reset no.such.thing", isn't very ergonomic.
392
457
- Will merge to 'next'?
458
- source: <20250918-pks-config-color-v3-0-08ea618cae26@pks.im>
393
+ Will merge to 'next'.
394
+ source: <20250922-pks-config-color-v4-0-28b7d2697eed@pks.im>
395
396
397
* ps/meson-build-docs (2025-09-11) 3 commits
@@ -466,7 +402,7 @@ well with other topics in 'seen' (and of course 'next' and
402
The build procedure based on meson learned a target to only build
403
documentation, similar to "make doc".
404
469
- Comments?
405
+ Will merge to 'next'.
406
source: <20250911-b4-pks-meson-docs-target-v1-0-a92c666ecef9@pks.im>
407
408
@@ -493,7 +429,7 @@ well with other topics in 'seen' (and of course 'next' and
429
create many objects at once in a transaction and abstract it into
430
the generic object layer.
431
496
- Will merge to 'next'?
432
+ Will merge to 'next'.
433
source: <20250916182938.2193476-1-jltobler@gmail.com>
434
435
@@ -504,21 +440,22 @@ well with other topics in 'seen' (and of course 'next' and
440
"git fast-import" learned that "--signed-commits=<how>" option that
441
corresponds to that of "git fast-export".
442
507
- Will merge to 'next'?
443
+ Will merge to 'next'.
444
source: <20250917181427.3193500-1-christian.couder@gmail.com>
445
446
447
* pw/3.0-default-initial-branch-to-main (2025-09-10) 4 commits
512
- - t0613: stop setting default initial branch
513
- - t9902: switch default branch name to main
514
- - t4013: switch default branch name to main
515
- - breaking-changes: switch default branch to main
448
+ (merged to 'next' on 2025-09-22 at 01bbebdab6)
449
+ + t0613: stop setting default initial branch
450
+ + t9902: switch default branch name to main
451
+ + t4013: switch default branch name to main
452
+ + breaking-changes: switch default branch to main
453
(this branch is used by jc/3.0-default-initial-branch-to-main-addendum.)
454
455
Declare that "git init" that is not otherwise configured uses
456
'main' as the initial branch, not 'master', starting Git 3.0.
457
521
- Will merge to 'next'.
458
+ Will merge to 'master'.
459
source: <cover.1757518141.git.phillip.wood@dunelm.org.uk>
460
461
@@ -550,7 +487,7 @@ well with other topics in 'seen' (and of course 'next' and
487
Dip our toes a bit to (optionally) use Rust implemented helper
488
called from our C code.
489
553
- Ejected for now, to give preference to en/*rust* topics.
490
+ Retracted, to join forces in en/*rust* topic.
491
source: <20250915-b4-pks-rust-breaking-change-v5-0-dc3a32fbb216@pks.im>
492
493
@@ -568,7 +505,7 @@ well with other topics in 'seen' (and of course 'next' and
505
"git refs optimize" is added for not very well explained reason
506
despite it does the same thing as "git pack-refs"...
507
571
- Comments?
508
+ Will merge to 'next'.
509
source: <20250919082647.535213-1-meetsoni3017@gmail.com>
510
511
@@ -583,7 +520,7 @@ well with other topics in 'seen' (and of course 'next' and
520
array index that would only fit in size_t but not int or ssize_t
521
to achieve unstated goal.
522
586
- Will merge to 'next'?
523
+ Will merge to 'next'.
524
source: <aMp8yNFiXDyk2hP4@ArchLinux>
525
526
@@ -608,7 +545,7 @@ well with other topics in 'seen' (and of course 'next' and
545
Code clean-up around the in-core list of all the pack files and
546
object database(s).
547
611
- Comments?
548
+ Expecting a reroll.
549
cf. <aMe_Zu1osrfDnSYL@pks.im>
550
source: <20250915-b4-pks-packfiles-store-v5-0-d6340350934f@pks.im>
551
@@ -623,7 +560,7 @@ well with other topics in 'seen' (and of course 'next' and
560
backend is used for ref storage, by failing only the ones that are
561
involved in the conflict while allowing others.
562
626
- Will merge to 'next'?
563
+ Will merge to 'next'.
564
source: <20250917-587-git-fetch-1-fails-fetches-on-case-insensitive-repositories-v4-0-da3c74a08ed0@gmail.com>
565
566
@@ -641,7 +578,8 @@ well with other topics in 'seen' (and of course 'next' and
578
579
Use Rust-friendly types in xdiff code.
580
644
- Comments?
581
+ Expecting a reroll.
582
+ cf. <CAH=ZcbA5hAM9kmO410KzVW7RXWWiwX2oJk6GGPP+6oVYatRVOw@mail.gmail.com>
583
source: <pull.2048.git.git.1757274320.gitgitgadget@gmail.com>
584
585
@@ -656,7 +594,7 @@ well with other topics in 'seen' (and of course 'next' and
594
595
Doc updates.
596
659
- Will merge to 'next'?
597
+ Will merge to 'next'.
598
cf. <236a79f4-e9a2-4335-bbff-79ae0cc67e9b@app.fastmail.com>
599
source: <pull.1962.v4.git.1757531669.gitgitgadget@gmail.com>
600
@@ -675,7 +613,7 @@ well with other topics in 'seen' (and of course 'next' and
613
Update "do you still use it?" message given by a command that is
614
deeply deprecated and allow us to suggest alternatives.
615
678
- Will merge to 'next'?
616
+ Will merge to 'next'.
617
source: <cover.1758139856.short.code@khaugsbakk.name>
618
619
@@ -708,5 +646,5 @@ well with other topics in 'seen' (and of course 'next' and
646
prune otherwise unused working-tree files that are outside the
647
areas of interest.
648
711
- Will merge to 'next'?
649
+ Will merge to 'next'.
650
source: <pull.1941.v3.git.1757673011.gitgitgadget@gmail.com>