What's cooking (2026/02 #01)
Junio C Hamano committed
Feb 2, 2026 at 08:33 UTC
376d73e2feef5f5bb7b622b59f47d6b4fee0132a
1 file changed
+50
-40
whats-cooking.txt
+50
-40
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Jan 2026, #10)
3
-X-master-at: ea717645d199f6f1b66058886475db3e8c9330e9
4
-X-next-at: 66b2238f5c17644ddf15f75a53c76faeca6d9f1e
2
+Subject: What's cooking in git.git (Feb 2026, #01)
3
+X-master-at: 67ad42147a7acc2af6074753ebd03d904476118f
4
+X-next-at: 85a36ad7943cb5a815d80ffafbe53e236af879ba
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Jan 2026, #10)
7
+What's cooking in git.git (Feb 2026, #01)
8
-----------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -21,8 +21,8 @@ Copies of the source code to Git live in many repositories, and the
21
following is a list of the ones I push into or their mirrors. Some
22
repositories have only a subset of branches.
23
24
-Git 2.53-rc2 has been tagged, with one topic reverted recently due
25
-to a regression. Please keep hunting for regressions.
24
+Git 2.53 has been tagged. Let's wait to see if there are regression
25
+reports from the real world and then start the new cycle.
26
27
With maint, master, next, seen, todo:
28
@@ -51,6 +51,15 @@ Release tarballs are available at:
51
--------------------------------------------------
52
[New Topics]
53
54
+* sp/show-index-warn-fallback (2026-01-30) 2 commits
55
+ - show-index: use gettext wrapping in user facing error messages
56
+ - show-index: warn when falling back to SHA-1 outside a repository
57
+
58
+ source: <20260130153603.290196-1-shreyanshpaliwalcmsmn@gmail.com>
59
+
60
+--------------------------------------------------
61
+[Cooking]
62
+
63
* jc/checkout-switch-restore (2026-01-29) 2 commits
64
- checkout: tell "parse_remote_branch" which command is calling it
65
- checkout: pass program-readable token to unified "main"
@@ -80,7 +89,7 @@ Release tarballs are available at:
89
source: <20260128234519.2721179-1-jltobler@gmail.com>
90
91
83
-* ps/for-each-ref-in-fixes (2026-01-29) 4 commits
92
+* ps/for-each-ref-in-fixes (2026-01-30) 4 commits
93
- bisect: simplify string_list memory handling
94
- bisect: fix misuse of `refs_for_each_ref_in()`
95
- pack-bitmap: fix bug with exact ref match in "pack.preferBitmapTips"
@@ -88,22 +97,18 @@ Release tarballs are available at:
97
98
A handful of places used refs_for_each_ref_in() API incorrectly,
99
which has been corrected.
91
-
92
- Need any more work on pack-bitmap side?
93
- cf. <xmqq7bt0cqec.fsf@gitster.g>
94
- source: <20260128-b4-pks-fix-for-each-ref-in-misuse-v1-0-deccae3ea725@pks.im>
100
+ source: <20260130-b4-pks-fix-for-each-ref-in-misuse-v2-0-0449b198a681@pks.im>
101
102
97
-* ty/perf-3400-optim (2026-01-28) 1 commit
98
- - t/perf/p3400: speed up setup using fast-import
103
+* ty/perf-3400-optim (2026-01-30) 1 commit
104
+ (merged to 'next' on 2026-02-01 at 6c019af192)
105
+ + t/perf/p3400: speed up setup using fast-import
106
107
Improve set-up time of a perf test.
108
102
- Comments?
103
- source: <20260128160717.611391-1-a3205153416@gmail.com>
109
+ Will cook in 'next'.
110
+ source: <20260130170123.642344-1-a3205153416@gmail.com>
111
105
---------------------------------------------------
106
-[Cooking]
112
113
* ja/doc-synopsis-style-even-more (2026-01-26) 4 commits
114
- doc: convert git-show to synopsis style
@@ -114,18 +119,20 @@ Release tarballs are available at:
119
A handful of documentation pages have been modernized to use the
120
"synopsis" style.
121
117
- Will merge to 'next'?
122
+ Expecting a reroll.
123
+ cf. <13939780.uLZWGnKmhe@piment-oiseau>
124
source: <pull.2036.v2.git.1769462744.gitgitgadget@gmail.com>
125
126
127
* ac/string-list-sort-u-and-tests (2026-01-29) 2 commits
122
- - string-list: add string_list_sort_u() that mimics "sort -u"
123
- - u-string-list: add unit tests for string-list methods
128
+ (merged to 'next' on 2026-01-30 at 742890e56f)
129
+ + string-list: add string_list_sort_u() that mimics "sort -u"
130
+ + u-string-list: add unit tests for string-list methods
131
132
The string_list API gains a new helper, string_list_sort_u(), and
133
new unit tests to extend coverage.
134
128
- Will merge to 'next'.
135
+ Will cook in 'next'.
136
source: <20260125201500.63904-2-amishhhaaaa@gmail.com>
137
138
@@ -191,7 +198,8 @@ Release tarballs are available at:
198
Instead of hardcoded 'origin', use the configured default remote
199
when fetching from submodules.
200
194
- Expecting a review response.
201
+ Expecting a reroll.
202
+ cf. <xmqqms23lpn2.fsf@gitster.g>
203
source: <20260122152722.866341-1-nasser.grainawi@oss.qualcomm.com>
204
205
@@ -248,8 +256,8 @@ Release tarballs are available at:
256
The final clean-up phase of the diff output could turn the result of
257
histogram diff algorithm suboptimal, which has been corrected.
258
251
- Expecting a review response.
252
- cf. <4fa413ae-f2a4-4de2-a2fb-0b1db379750b@gmail.com>
259
+ Expecting a reroll.
260
+ cf. <CAHTeOx-TLwqbcdGcb2drD4vE6D3M93EPMjcAeTNR+XNTbmTVZg@mail.gmail.com>
261
source: <pull.2120.git.git.1765054287938.gitgitgadget@gmail.com>
262
263
@@ -281,7 +289,7 @@ Release tarballs are available at:
289
source: <20260120-toon-last-modified-zzzz-v3-0-9bffd4968b0e@iotcl.com>
290
291
284
-* tc/last-modified-not-a-tree (2026-01-27) 4 commits
292
+* tc/last-modified-not-a-tree (2026-01-30) 4 commits
293
- last-modified: verify revision argument is a commit-ish
294
- last-modified: remove double error message
295
- last-modified: fix memory leak when more than one commit is given
@@ -290,9 +298,8 @@ Release tarballs are available at:
298
Giving "git last-modified" a tree (not a commit-ish) died an
299
uncontrolled death, which has been corrected.
300
293
- Expecting a reroll.
294
- cf. <87v7gkqxb0.fsf@iotcl.com>
295
- source: <20260127-toon-last-modified-tree-v5-0-38d18a0956d4@iotcl.com>
301
+ Will merge to 'next'?
302
+ source: <20260130-toon-last-modified-tree-v6-0-db827e5df985@iotcl.com>
303
304
305
* sp/myfirstcontribution-include-update (2026-01-12) 1 commit
@@ -323,18 +330,19 @@ Release tarballs are available at:
330
331
332
* kn/ref-batch-output-error-reporting-fix (2026-01-25) 6 commits
326
- - fetch: delay user information post committing of transaction
327
- - receive-pack: utilize rejected ref error details
328
- - fetch: utilize rejected ref error details
329
- - update-ref: utilize rejected error details if available
330
- - refs: add rejection detail to the callback function
331
- - refs: skip to next ref when current ref is rejected
333
+ (merged to 'next' on 2026-01-30 at fe8044c396)
334
+ + fetch: delay user information post committing of transaction
335
+ + receive-pack: utilize rejected ref error details
336
+ + fetch: utilize rejected ref error details
337
+ + update-ref: utilize rejected error details if available
338
+ + refs: add rejection detail to the callback function
339
+ + refs: skip to next ref when current ref is rejected
340
341
A handful of code paths that started using batched ref update API
342
(after Git 2.51 or so) lost detailed error output, which have been
343
corrected.
344
337
- Will merge to 'next'?
345
+ Will cook in 'next'.
346
source: <20260125-633-regression-lost-diagnostic-message-when-pushing-non-commit-objects-to-refs-heads-v5-0-d58f3a9edf98@gmail.com>
347
348
@@ -385,14 +393,15 @@ Release tarballs are available at:
393
394
395
* ps/validate-prefix-in-subtree-split (2026-01-15) 1 commit
388
- - subtree: validate --prefix against commit in split
396
+ (merged to 'next' on 2026-01-30 at 70c03b7148)
397
+ + subtree: validate --prefix against commit in split
398
399
"git subtree split --prefix=P <commit>" now checks the prefix P
400
against the tree of the (potentially quite different from the
401
current working tree) given commit.
402
394
- Expecting a reroll?
395
- source: <20260115122652.18673-2-pushkarkumarsingh1970@gmail.com>
403
+ Will cook in 'next'.
404
+ source: <20260115175403.3971-3-pushkarkumarsingh1970@gmail.com>
405
406
407
* sp/shallow-deepen-relative-fix (2026-01-16) 2 commits
@@ -531,12 +540,13 @@ Release tarballs are available at:
540
541
542
* sb/doc-worktree-prune-expire-improvement (2026-01-27) 1 commit
534
- - worktree: clarify that --expire only affects missing worktrees
543
+ (merged to 'next' on 2026-01-30 at faf2e087b8)
544
+ + worktree: clarify that --expire only affects missing worktrees
545
546
The help text and the documentation for the "--expire" option of
547
"git worktree [list|prune]" have been improved.
548
539
- Will merge to 'next'?
549
+ Will cook in 'next'.
550
source: <pull.2135.v3.git.git.1769578785381.gitgitgadget@gmail.com>
551
552