What's cooking (2026/06 #06)
Junio C Hamano committed
Jun 17, 2026 at 09:17 UTC
f9b08c9b285c9154e41b9f5fce7506018b83dfcb
1 file changed
+251
-300
whats-cooking.txt
+251
-300
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Jun 2026, #05)
3
-X-master-at: 700432b2ba22603a0bcb71475c9c333d17c9b0d1
4
-X-next-at: 65d90a03286dc77b5f6461c448f51d024b3fee22
2
+Subject: What's cooking in git.git (Jun 2026, #06)
3
+X-master-at: 4621f8ce5e9b97aa2e8d0d9ffe9d25df2471074d
4
+X-next-at: 3b0662c7b3a4a6dab9e3cb8a89039457b92b29fd
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Jun 2026, #05)
7
+What's cooking in git.git (Jun 2026, #06)
8
-----------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -17,10 +17,16 @@ A topic without enough support may be discarded after a long period
17
of no activity (of course they can be resubmitted when new interests
18
arise).
19
20
-A preview release Git 2.55-rc0 has been tagged and pushed out. There
21
-may be a few more topics in 'next' and possibly outside 'next' that
22
-we may want to include in the release that I didn't manage or I
23
-forgot (please let me know).
20
+Git 2.55-rc1 has been tagged and pushed out. There may be a few
21
+more topics in 'next' that we may want to include in the release
22
+that I didn't manage or I forgot (please let me know), but basically
23
+this development cycle is over, the tree is feature-frozen, and
24
+remaining topics in 'next' will stay in "Will cook in 'next'"
25
+instead of "Will merge to 'master'" state. We'd want to force
26
+ourselves to concentrate on addressing topics that are important
27
+fixes but still in the "Needs review" state, and of course, find any
28
+correct any regressions relative to Git 2.54, until we are ready to
29
+tag Git 2.55 final.
30
31
Copies of the source code to Git live in many repositories, and the
32
following is a list of the ones I push into or their mirrors. Some
@@ -50,116 +56,195 @@ Release tarballs are available at:
56
57
https://www.kernel.org/pub/software/scm/git/
58
59
+--------------------------------------------------
60
+[New Topics]
61
+
62
+* mh/fetch-follow-remote-head-config (2026-06-16) 7 commits
63
+ - fetch: fixup a misaligned comment
64
+ - fetch: add configuration variable fetch.followRemoteHEAD
65
+ - fetch: refactor do_fetch handling of followRemoteHEAD
66
+ - fetch: rename function report_set_head
67
+ - t5510: cleanup remote in followRemoteHEAD dangling ref test
68
+ - doc: explain fetchRemoteHEADWarn advice
69
+ - fetch: fixup set_head advice for warn-if-not-branch
70
+
71
+ The `fetch.followRemoteHEAD` configuration variable has been added to
72
+ provide a default for the per-remote `remote.<name>.followRemoteHEAD`
73
+ setting.
74
+
75
+ Will merge to 'next'?
76
+ source: <20260616222606.1003521-1-m@lfurio.us>
77
+
78
+
79
+* ps/refs-writing-subcommands (2026-06-17) 5 commits
80
+ - builtin/refs: add "rename" subcommand
81
+ - builtin/refs: add "create" subcommand
82
+ - builtin/refs: add "update" subcommand
83
+ - builtin/refs: add "delete" subcommand
84
+ - builtin/refs: drop `the_repository`
85
+
86
+ The "git refs" toolbox has been extended with new "create", "delete",
87
+ "update", and "rename" subcommands to create, delete, update, and
88
+ rename references, respectively.
89
+
90
+ Will merge to 'next'?
91
+ source: <20260617-pks-refs-writing-subcommands-v2-0-07f3d18336f9@pks.im>
92
+
93
+
94
+* po/hash-object-size-t (2026-06-16) 6 commits
95
+ - hash-object: add a >4GB/LLP64 test case using filtered input
96
+ - hash-object: add another >4GB/LLP64 test case
97
+ - hash-object --stdin: verify that it works with >4GB/LLP64
98
+ - hash algorithms: use size_t for section lengths
99
+ - object-file.c: use size_t for header lengths
100
+ - hash-object: demonstrate a >4GB/LLP64 problem
101
+
102
+ Support for hashing loose or packed objects larger than 4GB on Windows
103
+ and other LLP64 platforms has been improved by converting object header
104
+ buffers and data-handling functions from 'unsigned long' to 'size_t'.
105
+
106
+ Will merge to 'next'?
107
+ source: <pull.2138.v2.git.1781621398.gitgitgadget@gmail.com>
108
+
109
--------------------------------------------------
110
[Graduated to 'master']
111
56
-* ak/typofixes (2026-05-31) 1 commit
57
- (merged to 'next' on 2026-06-09 at 40de2e7b90)
58
- + doc: fix typos via codespell
59
-
60
- Typofixes.
61
- cf. <3398ef40-1547-4324-2cfc-97b9e2b24854@gmx.de>
62
- cf. <xmqq8q8p1ese.fsf@gitster.g>
63
- source: <20260531184428.55905-1-algonell@gmail.com>
64
- source: <20260506101631.18127-1-algonell@gmail.com>
65
- source: <3398ef40-1547-4324-2cfc-97b9e2b24854@gmx.de>
66
-
67
-
68
-* am/doc-tech-hash-typofix (2026-06-05) 1 commit
69
- (merged to 'next' on 2026-06-09 at aeaf2363f8)
70
- + doc: fix typo in GIT_ALTERNATE_OBJECT_DIRECTORIES
71
-
72
- Typofix.
73
- cf. <aiZo9FqsdKrhz0gA@pks.im>
74
- source: <20260605172643.8796-1-amonakov@ispras.ru>
75
-
76
-
77
-* hn/config-typo-advice (2026-06-02) 2 commits
78
- (merged to 'next' on 2026-06-09 at 5149e69e3e)
79
- + config: improve diagnostic for "set" with missing value
80
- + config: add git_config_key_is_valid() for quiet validation
81
-
82
- "git config foo.bar=baz" is not likely to be a request to read the
83
- value of such a variable with '=' in its name; rather it is plausible
84
- that the user meant "git config set foo.bar baz". Give advice when
85
- giving an error message.
86
- cf. <xmqq1penqfg2.fsf@gitster.g>
87
- source: <pull.2302.v6.git.git.1780425808.gitgitgadget@gmail.com>
88
-
89
-
90
-* jc/submitting-patches-cover-letter (2026-06-02) 2 commits
91
- (merged to 'next' on 2026-06-09 at 42b2538a2a)
92
- + SubmittingPatches: describe cover letter
93
- + SubmittingPatches: separate typofixes section
94
-
95
- Guidelines on how to write a cover letter for a multi-patch series
96
- have been added to SubmittingPatches, which also got a new marker
97
- to separate the section for typofixes.
98
- cf. <c54f3571-ff7b-4caa-b75d-a739ed87ec9d@gmail.com>
99
- cf. <aiEgUdnL8dkszKFn@pks.im>
100
- source: <20260602144304.3341000-1-gitster@pobox.com>
101
-
102
-
103
-* lo/doc-format-patch-subject-prefix (2026-06-04) 1 commit
104
- (merged to 'next' on 2026-06-09 at 58b2a20f6d)
105
- + Documentation: remove redundant 'instead' in --subject-prefix
106
-
107
- Wording used in "format-patch --subject-prefix" documentation
108
- has been improved.
109
-
110
- source: <20260604163510.36687-2-lucasseikioshiro@gmail.com>
111
-
112
-
113
-* ls/doc-raw-timestamp-prefix (2026-06-02) 1 commit
114
- (merged to 'next' on 2026-06-09 at 7198b6bb9d)
115
- + doc: document and test `@` prefix for raw timestamps
116
-
117
- Documentation and tests have been added to clarify that Git's internal
118
- raw timestamp format requires a `@` prefix for values less than
119
- 100,000,000 to prevent ambiguity with other formats like YYYYMMDD.
120
- cf. xmqqmrxdxq1r.fsf@gitster.g>
121
- source: <20260602081924.673763-2-dev@luna.gl>
122
-
123
-
124
-* ob/more-repo-config-values (2026-06-02) 8 commits
125
- (merged to 'next' on 2026-06-09 at 3d0b057aee)
126
- + environment: move "warn_on_object_refname_ambiguity" into `struct repo_config_values`
127
- + environment: move "sparse_expect_files_outside_of_patterns" into `struct repo_config_values`
128
- + environment: move "core_sparse_checkout_cone" into `struct repo_config_values`
129
- + environment: move "precomposed_unicode" into `struct repo_config_values`
130
- + environment: move "pack_compression_level" into `struct repo_config_values`
131
- + environment: move `zlib_compression_level` into `struct repo_config_values`
132
- + environment: move "check_stat" into `struct repo_config_values`
133
- + environment: move "trust_ctime" into `struct repo_config_values`
134
-
135
- Many core configuration variables have been migrated from global
136
- variables into 'repo_config_values' to tie them to a specific
137
- repository instance, avoiding cross-repository state leakage.
138
-
139
- source: <20260602170921.35869-1-belkid98@gmail.com>
140
-
141
-
142
-* ps/setup-centralize-odb-creation (2026-06-04) 9 commits
143
- (merged to 'next' on 2026-06-09 at a1f23cb38c)
144
- + setup: construct object database in `apply_repository_format()`
145
- + repository: stop reading loose object map twice on repo init
146
- + setup: stop initializing object database without repository
147
- + setup: stop creating the object database in `setup_git_env()`
148
- + repository: stop initializing the object database in `repo_set_gitdir()`
149
- + setup: deduplicate logic to apply repository format
150
- + setup: drop `setup_git_env()`
151
- + t0001: plug test gaps for git-init(1) with GIT_OBJECT_DIRECTORY
152
- + Merge branch 'ps/setup-wo-the-repository' into ps/setup-centralize-odb-creation
153
- (this branch is used by ps/refs-avoid-chdir-notify-reparent and ps/setup-drop-global-state.)
154
-
155
- The setup logic to discover and configure repositories has been
156
- refactored, and the initialization of the object database has been
157
- centralized.
158
- cf. <CAOLa=ZQwVbLsOcajaxQwtkTPm=4St7EiGEEyL6_B0o3Tt1v1pw@mail.gmail.com>
159
- source: <20260604-b4-pks-setup-centralize-odb-creation-v3-0-0691834f318a@pks.im>
112
+* ab/index-pack-retain-child-bases (2026-06-01) 1 commit
113
+ (merged to 'next' on 2026-06-12 at 625f76ac4c)
114
+ + index-pack: retain child bases in delta cache
115
+
116
+ "git index-pack" has been optimized by retaining child bases in the
117
+ delta cache instead of immediately freeing them, letting the existing
118
+ cache limit policy decide eviction.
119
+ source: <pull.2131.v2.git.1780330402264.gitgitgadget@gmail.com>
120
+
121
+
122
+* jd/unpack-trees-wo-the-repository (2026-03-31) 1 commit
123
+ (merged to 'next' on 2026-06-11 at 3d7788721e)
124
+ + unpack-trees: use repository from index instead of global
125
+
126
+ A handful of inappropriate uses of the_repository have been
127
+ rewritten to use the right repository structure instance in the
128
+ unpack-trees.c codepath.
129
+ cf. <xmqqqzmfz91r.fsf@gitster.g>
130
+ source: <pull.2258.v2.git.git.1774971267.gitgitgadget@gmail.com>
131
+
132
+
133
+* jk/describe-contains-all-match-fix (2026-06-01) 1 commit
134
+ (merged to 'next' on 2026-06-11 at a95871538b)
135
+ + describe: fix --exclude, --match with --contains and --all
136
+
137
+ The 'git describe --contains --all' command has been fixed to
138
+ properly honor the '--match' and '--exclude' options by passing
139
+ them down to 'git name-rev' with the appropriate reference
140
+ prefixes.
141
+ source: <20260601233727.43558-1-jacob.e.keller@intel.com>
142
+
143
+
144
+* js/osxkeychain-build-wo-rust (2026-06-17) 1 commit
145
+ (merged to 'next' on 2026-06-17 at d5f6cec43d)
146
+ + osxkeychain: fix build with Rust
147
+
148
+ Build fix.
149
+ source: <pull.2154.git.1781691074710.gitgitgadget@gmail.com>
150
+
151
+
152
+* js/win-kill-child-more-gently (2026-06-04) 2 commits
153
+ (merged to 'next' on 2026-06-11 at b4a2299e7e)
154
+ + mingw: really handle SIGINT
155
+ + mingw: kill child processes in a gentler way
156
+
157
+ Advanced emulation of kill() used on Windows in GfW has been
158
+ upstreamed to improve the symptoms like left-behind .lock files and
159
+ that fails to let the child clean-up itself when it gets killed.
160
+ source: <pull.2130.git.1780590261.gitgitgadget@gmail.com>
161
+
162
+
163
+* kk/streaming-walk-pqueue (2026-05-27) 3 commits
164
+ (merged to 'next' on 2026-06-11 at 1466219fc9)
165
+ + revision: use priority queue for non-limited streaming walks
166
+ + revision: introduce rev_walk_mode to clarify get_revision_1()
167
+ + pack-objects: call release_revisions() after cruft traversal
168
+
169
+ Streaming revision walks have been optimized by using a priority queue
170
+ for date-sorting commits, speeding up walks repositories with many
171
+ merges.
172
+ source: <pull.2127.git.1779897003.gitgitgadget@gmail.com>
173
+
174
+
175
+* mf/revision-max-count-oldest (2026-06-10) 2 commits
176
+ (merged to 'next' on 2026-06-11 at c89a71798a)
177
+ + bash-completions: add --max-count-oldest
178
+ (merged to 'next' on 2026-06-09 at 076600fa21)
179
+ + revision.c: implement --max-count-oldest
180
+
181
+ "git rev-list" (and "git log" family of commands) learned a new "--max-count-oldest"
182
+ that picks oldest N commits in the range instead of the usual newest.
183
+ source: <xmqq4ijm3p2x.fsf@gitster.g>
184
+
185
+
186
+* mm/subprocess-handshake-fix (2026-06-01) 1 commit
187
+ (merged to 'next' on 2026-06-11 at b649c3a97c)
188
+ + sub-process: use gentle handshake to avoid die() on startup failure
189
+
190
+ The subprocess handshake during startup has been made gentler by using
191
+ packet_read_line_gently() instead of packet_read_line() to prevent the
192
+ parent Git process from dying abruptly when a configured subprocess
193
+ (e.g., a clean/smudge filter) fails to start.
194
+ source: <pull.2133.v2.git.1780348848489.gitgitgadget@gmail.com>
195
+
196
+
197
+* ps/t7527-fix-tap-output (2026-06-04) 8 commits
198
+ (merged to 'next' on 2026-06-11 at b5a4cd26ee)
199
+ + t: let prove fail when parsing invalid TAP output
200
+ + t/lib-git-p4: silence output when killing p4d and its watchdog
201
+ + t/test-lib: silence EBUSY errors on Windows during test cleanup
202
+ + t7810: turn MB_REGEX check into a lazy prereq
203
+ + t7527: fix broken TAP output
204
+ + ci: unify Linux images across GitLab and GitHub
205
+ + gitlab-ci: add missing Linux jobs
206
+ + gitlab-ci: rearrange Linux jobs to match GitHub's order
207
+
208
+ A recent regression in t7527 that broke TAP output has been fixed,
209
+ some other test noise that also broke TAP output has been silenced,
210
+ and 'prove' is now configured to fail on invalid TAP output to
211
+ prevent future regressions.
212
+ source: <20260604-pks-t7527-fix-tap-output-v3-0-7d766ed481e4@pks.im>
213
+
214
+
215
+* ta/typofixes (2026-06-04) 1 commit
216
+ (merged to 'next' on 2026-06-11 at dfb63ded01)
217
+ + docs: fix typos
218
+
219
+ Typofixes
220
+ cf. <xmqqh5ncvfsu.fsf@gitster.g>
221
+ source: <20260604131457.19215-1-taahol@utu.fi>
222
+
223
+
224
+* wy/docs-typofixes (2026-05-29) 1 commit
225
+ (merged to 'next' on 2026-06-11 at bd53c91110)
226
+ + docs: fix typos and grammar
227
+
228
+ Various typos, grammatical errors, and duplicated words in both
229
+ documentation and code comments have been corrected.
230
+ source: <7b502e20e9495cd4720496bd6738a1fbeb453410.1780041658.git.wy@wyuan.org>
231
232
--------------------------------------------------
162
-[New Topics]
233
+[Stalled]
234
+
235
+* jt/config-lock-timeout (2026-05-17) 1 commit
236
+ - config: retry acquiring config.lock, configurable via core.configLockTimeout
237
+
238
+ Configuration file locking now retries for a short period, avoiding
239
+ failures when multiple processes attempt to update the configuration
240
+ simultaneously.
241
+
242
+ Waiting for response(s) to review comment(s) for too long, stalled.
243
+ cf. <agrIrGwSMFlKTx9x@pks.im>
244
+ source: <20260517132111.1014901-1-joerg@thalheim.io>
245
+
246
+--------------------------------------------------
247
+[Cooking]
248
249
* kh/submittingpatches-trailers (2026-06-10) 6 commits
250
- SubmittingPatches: note that trailer order matters
@@ -173,7 +258,7 @@ Release tarballs are available at:
258
encourage use of standard trailers.
259
260
Waiting for response(s) to review comment(s).
176
- cf. <xmqqse6tnho1.fsf@gitster.g>
261
+ cf. <ajJNjOYMVDwL52zY@pks.im>
262
source: <CV_SubPatches_trailers.8f3@msgid.xyz>
263
264
@@ -230,25 +315,27 @@ Release tarballs are available at:
315
316
317
* en/commit-graph-timestamp-fix (2026-06-13) 1 commit
233
- - commit-graph: use timestamp_t for max parent generation accumulator
318
+ (merged to 'next' on 2026-06-16 at 13248b8196)
319
+ + commit-graph: use timestamp_t for max parent generation accumulator
320
321
compute_reachable_generation_numbers() in commit-graph used a 32-bit
322
integer to accumulate parent generations, which is OK for generation
323
number v1 (topological levels), but with generation number v2
324
(adjusted committer timestamps), it truncated timestamps beyond
325
2106. Fixed by widening the accumulator to timestamp_t.
240
- Will merge to 'next'?
241
- cf. <ai-zzWn9Ls6-j9h8@pks.im>
326
+
327
+ Will merge to 'master'.
328
+ cf. <09e50180-e165-48d8-a9d0-485283342f5c@gmail.com>
329
source: <pull.2148.git.1781420271100.gitgitgadget@gmail.com>
330
331
332
* mm/test-grep-lint (2026-06-12) 6 commits
246
- . t: add greplint to detect bare grep assertions
247
- . t: convert grep assertions to test_grep
248
- . t: fix Lexer line count for $() inside double-quoted strings
249
- . t: extract chainlint's parser into shared module
250
- . t: fix grep assertions missing file arguments
251
- . t/README: document test_grep helper
333
+ - t: add greplint to detect bare grep assertions
334
+ - t: convert grep assertions to test_grep
335
+ - t: fix Lexer line count for $() inside double-quoted strings
336
+ - t: extract chainlint's parser into shared module
337
+ - t: fix grep assertions missing file arguments
338
+ - t/README: document test_grep helper
339
340
Needs review.
341
source: <pull.2135.v2.git.1781323575.gitgitgadget@gmail.com>
@@ -263,22 +350,25 @@ Release tarballs are available at:
350
- patch-delta: use size_t for sizes
351
- compat/msvc: use _chsize_s for ftruncate
352
353
+ Needs review.
354
source: <pull.2137.v2.git.1781524349.gitgitgadget@gmail.com>
355
356
357
* kw/gitattributes-typofix (2026-06-15) 1 commit
358
- gitattributes: fix eol attribute for Perl scripts
359
360
+ Will merge to 'next'.
361
+ cf. <ai-5vfY8D84UhsB4@pks.im>
362
source: <pull.2151.v2.git.1781510039164.gitgitgadget@gmail.com>
363
364
365
* rs/cat-file-default-format-optim (2026-06-14) 1 commit
366
- cat-file: speed up default format
367
368
+ Will merge to 'next'.
369
+ cf. <20260615165326.GA91269@coredump.intra.peff.net>
370
source: <5a7ed929-6fe0-496c-83bd-65dee57c2241@web.de>
371
280
---------------------------------------------------
281
-[Cooking]
372
373
* js/parseopt-subcommand-autocorrection (2026-04-27) 11 commits
374
- SQUASH???
@@ -296,8 +386,8 @@ Release tarballs are available at:
386
The parse-options library learned to auto-correct misspelled
387
subcommand names.
388
299
- Expecting a reroll for too long. stalled.
300
- cf. <SY0P300MB0801E50FCB7EB2F45CD15208CE042@SY0P300MB0801.AUSP300.PROD.OUTLOOK.COM>
389
+ Waiting for response(s) to review comment(s).
390
+ cf. <xmqq33yzd9yf.fsf@gitster.g>
391
source: <SY0P300MB0801677A2A1E0FD38D06A841CE2A2@SY0P300MB0801.AUSP300.PROD.OUTLOOK.COM>
392
393
@@ -319,8 +409,8 @@ Release tarballs are available at:
409
410
API clean-up.
411
322
- Waiting for response(s) to review comment(s).
323
- cf. <3a3d1dc4-341f-4276-a1ee-2972a885db84@gmail.com>
412
+ Retracted.
413
+ cf. <CAL71e4P3Oq08xVPZ+dxQ8L5PKekPJN0RsL4pTicom1og7-1D=A@mail.gmail.com>
414
source: <pull.2144.v2.git.1781178567862.gitgitgadget@gmail.com>
415
416
@@ -339,7 +429,8 @@ Release tarballs are available at:
429
source: <20260612-ref-filter-memoized-contains-v4-0-5ed39fd001dd@gmail.com>
430
431
342
-* tc/replay-linearize (2026-06-10) 3 commits
432
+* tc/replay-linearize (2026-06-16) 4 commits
433
+ - SQUASH??? prepare for mm/test-grep-lint
434
- replay: offer an option to linearize the commit topology
435
- replay: add helper to put entry into mapped_commits
436
- replay: refactor enum replay_mode into a bool
@@ -348,10 +439,8 @@ Release tarballs are available at:
439
linearize the replayed history, mimicking git rebase
440
--no-rebase-merges.
441
351
- Waiting for response(s) to review comment(s).
352
- cf. <xmqqjys6wcpo.fsf@gitster.g>
353
- cf. <CABPp-BGRi2obnqRGEY9pSMyvRbNGs8AdVUpZmr0C6vZSgHb=cg@mail.gmail.com>
354
- source: <20260610-toon-git-replay-drop-merges-v2-0-5714a71c6d83@iotcl.com>
442
+ Needs review.
443
+ source: <20260616-toon-git-replay-drop-merges-v3-0-153e9eb99ce1@iotcl.com>
444
445
446
* td/describe-tag-iteration (2026-06-10) 1 commit
@@ -397,7 +486,7 @@ Release tarballs are available at:
486
outcome is that `is_bare_repository()` has been updated to no longer
487
implicitly rely on `the_repository`.
488
400
- Will merge to 'master'.
489
+ Will cook in 'next'.
490
cf. <airVOrTboNDDGBak@denethor>
491
cf. <87ldckyygk.fsf@emacs.iotcl.com>
492
source: <20260611-b4-pks-setup-drop-global-state-v2-0-a6f7269c841d@pks.im>
@@ -434,20 +523,7 @@ Release tarballs are available at:
523
source: <xmqqo6hit6rn.fsf@gitster.g>
524
525
437
-* jd/unpack-trees-wo-the-repository (2026-03-31) 1 commit
438
- (merged to 'next' on 2026-06-11 at 3d7788721e)
439
- + unpack-trees: use repository from index instead of global
440
-
441
- A handful of inappropriate uses of the_repository have been
442
- rewritten to use the right repository structure instance in the
443
- unpack-trees.c codepath.
444
-
445
- Will merge to 'master'.
446
- cf. <xmqqqzmfz91r.fsf@gitster.g>
447
- source: <pull.2258.v2.git.git.1774971267.gitgitgadget@gmail.com>
448
-
449
-
450
-* ps/odb-source-packed (2026-06-09) 18 commits
526
+* ps/odb-source-packed (2026-06-16) 18 commits
527
- odb/source-packed: drop pointer to "files" parent source
528
- midx: refactor interfaces to work on "packed" source
529
- odb/source-packed: stub out remaining functions
@@ -471,7 +547,7 @@ Release tarballs are available at:
547
odb_source.
548
549
Needs review.
474
- source: <20260609-pks-odb-source-packed-v2-0-839089132c8b@pks.im>
550
+ source: <20260617-pks-odb-source-packed-v3-0-b5c7583cd795@pks.im>
551
552
553
* ps/transport-helper-tsan-fix (2026-06-09) 1 commit
@@ -489,30 +565,6 @@ Release tarballs are available at:
565
source: <20260609134741.4727-2-pushkarkumarsingh1970@gmail.com>
566
567
492
-* ta/typofixes (2026-06-04) 1 commit
493
- (merged to 'next' on 2026-06-11 at dfb63ded01)
494
- + docs: fix typos
495
-
496
- Typofixes
497
-
498
- Will merge to 'master'.
499
- cf. <xmqqh5ncvfsu.fsf@gitster.g>
500
- source: <20260604131457.19215-1-taahol@utu.fi>
501
-
502
-
503
-* js/win-kill-child-more-gently (2026-06-04) 2 commits
504
- (merged to 'next' on 2026-06-11 at b4a2299e7e)
505
- + mingw: really handle SIGINT
506
- + mingw: kill child processes in a gentler way
507
-
508
- Advanced emulation of kill() used on Windows in GfW has been
509
- upstreamed to improve the symptoms like left-behind .lock files and
510
- that fails to let the child clean-up itself when it gets killed.
511
-
512
- Will merge to 'master'.
513
- source: <pull.2130.git.1780590261.gitgitgadget@gmail.com>
514
-
515
-
568
* dl/posix-unused-warning-clang (2026-06-13) 3 commits
569
(merged to 'next' on 2026-06-15 at 1d7e627c24)
570
+ compat/posix.h: simplify GIT_GNUC_PREREQ() comparison
@@ -549,7 +601,7 @@ Release tarballs are available at:
601
been migrated into struct repo_config_values to tie them to
602
per-repository configuration state.
603
552
- Will merge to 'master'.
604
+ Will cook in 'next'.
605
cf. <CAP8UFD35Tiy1_fqpjq8P-z=ZhzR3MTiThqfCs977652umRoSEQ@mail.gmail.com>
606
cf. <xmqqse6uwdnz.fsf@gitster.g>
607
source: <20260610124353.149874-2-cat@malon.dev>
@@ -619,24 +671,11 @@ Release tarballs are available at:
671
documentation has been updated to recommend using it as a
672
streamlined method for submitting patches.
673
622
- Needs review.
674
+ Will merge to 'next'.
675
+ cf. <87eci7yomp.fsf@emacs.iotcl.com>
676
source: <20260615-pks-b4-v4-0-22cfca8f19c5@pks.im>
677
678
626
-* kk/streaming-walk-pqueue (2026-05-27) 3 commits
627
- (merged to 'next' on 2026-06-11 at 1466219fc9)
628
- + revision: use priority queue for non-limited streaming walks
629
- + revision: introduce rev_walk_mode to clarify get_revision_1()
630
- + pack-objects: call release_revisions() after cruft traversal
631
-
632
- Streaming revision walks have been optimized by using a priority queue
633
- for date-sorting commits, speeding up walks repositories with many
634
- merges.
635
-
636
- Will merge to 'master'.
637
- source: <pull.2127.git.1779897003.gitgitgadget@gmail.com>
638
-
639
-
679
* sn/rebase-update-refs-symrefs (2026-06-03) 1 commit
680
- rebase: skip branch symref aliases
681
@@ -651,42 +690,6 @@ Release tarballs are available at:
690
source: <pull.2126.v2.git.1780482436865.gitgitgadget@gmail.com>
691
692
654
-* jk/describe-contains-all-match-fix (2026-06-01) 1 commit
655
- (merged to 'next' on 2026-06-11 at a95871538b)
656
- + describe: fix --exclude, --match with --contains and --all
657
-
658
- The 'git describe --contains --all' command has been fixed to
659
- properly honor the '--match' and '--exclude' options by passing
660
- them down to 'git name-rev' with the appropriate reference
661
- prefixes.
662
-
663
- Will merge to 'master'.
664
- source: <20260601233727.43558-1-jacob.e.keller@intel.com>
665
-
666
-
667
-* wy/docs-typofixes (2026-05-29) 1 commit
668
- (merged to 'next' on 2026-06-11 at bd53c91110)
669
- + docs: fix typos and grammar
670
-
671
- Various typos, grammatical errors, and duplicated words in both
672
- documentation and code comments have been corrected.
673
-
674
- Will merge to 'master'.
675
- source: <7b502e20e9495cd4720496bd6738a1fbeb453410.1780041658.git.wy@wyuan.org>
676
-
677
-
678
-* ab/index-pack-retain-child-bases (2026-06-01) 1 commit
679
- (merged to 'next' on 2026-06-12 at 625f76ac4c)
680
- + index-pack: retain child bases in delta cache
681
-
682
- "git index-pack" has been optimized by retaining child bases in the
683
- delta cache instead of immediately freeing them, letting the existing
684
- cache limit policy decide eviction.
685
-
686
- Will merge to 'master'.
687
- source: <pull.2131.v2.git.1780330402264.gitgitgadget@gmail.com>
688
-
689
-
693
* mm/diff-process-hunks (2026-06-14) 6 commits
694
- blame: consult diff process for no-hunk detection
695
- diff: bypass diff process with --no-ext-diff and in format-patch
@@ -701,11 +704,13 @@ Release tarballs are available at:
704
while leaving all output formatting (word diff, color, blame, etc.) to
705
Git's standard pipeline.
706
704
- Needs review.
707
+ Expecting a reroll.
708
+ cf. <CAC2Qwm+P=fZOtpfMPeMiSXf3Afk6OLYpTP8Br78_PRA8WNL1Wg@mail.gmail.com>
709
source: <pull.2120.v4.git.1781463564.gitgitgadget@gmail.com>
710
711
708
-* tb/pack-path-walk-bitmap-delta-islands (2026-06-02) 5 commits
712
+* tb/pack-path-walk-bitmap-delta-islands (2026-06-15) 6 commits
713
+ - SQUASH???
714
- pack-objects: support `--delta-islands` with `--path-walk`
715
- pack-objects: extract `record_tree_depth()` helper
716
- pack-objects: support reachability bitmaps with `--path-walk`
@@ -719,6 +724,7 @@ Release tarballs are available at:
724
725
Waiting for response(s) to review comment(s).
726
cf. <849c659f-efa8-430a-bfac-0c26a3ed1aaa@gmail.com>
727
+ cf. <xmqqjyrzbjyf.fsf@gitster.g>
728
source: <cover.1780438896.git.me@ttaylorr.com>
729
730
@@ -749,20 +755,7 @@ Release tarballs are available at:
755
source: <pull.2132.v2.git.1780301856444.gitgitgadget@gmail.com>
756
757
752
-* mm/subprocess-handshake-fix (2026-06-01) 1 commit
753
- (merged to 'next' on 2026-06-11 at b649c3a97c)
754
- + sub-process: use gentle handshake to avoid die() on startup failure
755
-
756
- The subprocess handshake during startup has been made gentler by using
757
- packet_read_line_gently() instead of packet_read_line() to prevent the
758
- parent Git process from dying abruptly when a configured subprocess
759
- (e.g., a clean/smudge filter) fails to start.
760
-
761
- Will merge to 'master'.
762
- source: <pull.2133.v2.git.1780348848489.gitgitgadget@gmail.com>
763
-
764
-
765
-* jk/repo-info-path-keys (2026-06-14) 4 commits
758
+* jk/repo-info-path-keys (2026-06-15) 4 commits
759
- repo: add path.gitdir with absolute and relative suffix formatting
760
- repo: add path.commondir with absolute and relative suffix formatting
761
- rev-parse: use append_formatted_path() for path formatting
@@ -772,8 +765,9 @@ Release tarballs are available at:
765
absolute and relative paths for "gitdir" and "commondir", supported by
766
a new path-formatting helper extracted from "git rev-parse".
767
775
- Needs review.
776
- source: <20260615045112.50686-1-jayatheerthkulkarni2005@gmail.com>
768
+ Expecting a reroll.
769
+ cf. <CA+rGoLfhhRNrSReeJ1grhy+2K3BSrikTCNgGpCaGqc4fFp3Lfg@mail.gmail.com>
770
+ source: <20260616044953.184806-1-jayatheerthkulkarni2005@gmail.com>
771
772
773
* ps/history-drop (2026-06-15) 10 commits
@@ -796,36 +790,16 @@ Release tarballs are available at:
790
source: <20260615-b4-pks-history-drop-v6-0-2e329e536d78@pks.im>
791
792
799
-* jk/setup-gitfile-diag-fix (2026-06-01) 1 commit
800
- - read_gitfile_gently(): return non-repo path on error
793
+* jk/setup-gitfile-diag-fix (2026-06-16) 1 commit
794
+ - read_gitfile(): simplify NOT_A_REPO error message
795
796
A regression in the error diagnosis code for invalid .git files has
797
been fixed, avoiding a potential NULL-pointer crash when reporting
798
that a .git file does not point to a valid repository.
799
806
- Waiting for response(s) to review comment(s).
807
- cf. <xmqqeciezh0w.fsf@gitster.g>
808
- source: <20260602061159.GA693928@coredump.intra.peff.net>
809
-
810
-
811
-* ps/t7527-fix-tap-output (2026-06-04) 8 commits
812
- (merged to 'next' on 2026-06-11 at b5a4cd26ee)
813
- + t: let prove fail when parsing invalid TAP output
814
- + t/lib-git-p4: silence output when killing p4d and its watchdog
815
- + t/test-lib: silence EBUSY errors on Windows during test cleanup
816
- + t7810: turn MB_REGEX check into a lazy prereq
817
- + t7527: fix broken TAP output
818
- + ci: unify Linux images across GitLab and GitHub
819
- + gitlab-ci: add missing Linux jobs
820
- + gitlab-ci: rearrange Linux jobs to match GitHub's order
821
-
822
- A recent regression in t7527 that broke TAP output has been fixed,
823
- some other test noise that also broke TAP output has been silenced,
824
- and 'prove' is now configured to fail on invalid TAP output to
825
- prevent future regressions.
826
-
827
- Will merge to 'master'.
828
- source: <20260604-pks-t7527-fix-tap-output-v3-0-7d766ed481e4@pks.im>
800
+ Will merge to 'next'?
801
+ cf. <xmqqjyry4hax.fsf@gitster.g>
802
+ source: <20260616123516.GA2301231@coredump.intra.peff.net>
803
804
805
* kh/doc-trailers (2026-06-10) 10 commits
@@ -891,23 +865,11 @@ Release tarballs are available at:
865
diverged from its push branch has been updated to suggest "git pull
866
<remote> <branch>".
867
894
- Will merge to 'master'.
868
+ Will cook in 'next'.
869
cf. <xmqq7bo6xuok.fsf@gitster.g>
870
source: <pull.2301.v4.git.git.1779372367317.gitgitgadget@gmail.com>
871
872
899
-* jt/config-lock-timeout (2026-05-17) 1 commit
900
- - config: retry acquiring config.lock, configurable via core.configLockTimeout
901
-
902
- Configuration file locking now retries for a short period, avoiding
903
- failures when multiple processes attempt to update the configuration
904
- simultaneously.
905
-
906
- Waiting for response(s) to review comment(s).
907
- cf. <agrIrGwSMFlKTx9x@pks.im>
908
- source: <20260517132111.1014901-1-joerg@thalheim.io>
909
-
910
-
873
* hn/branch-prune-merged (2026-06-15) 7 commits
874
- branch: add --dry-run for --delete-merged
875
- branch: add branch.<name>.deleteMerged opt-out
@@ -921,7 +883,9 @@ Release tarballs are available at:
883
local branches that have already been merged to the remote-tracking
884
branches they track.
885
924
- Needs review.
886
+ Waiting for response(s) to review comment(s).
887
+ cf. <78b6dfdd-df61-4c44-96eb-b527cb26243c@gmail.com>
888
+ cf. <f68e2a11-02a5-47b9-a01a-458eba821c37@gmail.com>
889
source: <pull.2285.v15.git.git.1781542042.gitgitgadget@gmail.com>
890
891
@@ -941,7 +905,7 @@ Release tarballs are available at:
905
remotes via the promisor.acceptFromServerURL configuration
906
variable.
907
944
- Will merge to 'master'.
908
+ Will cook in 'next'.
909
cf. <877bo7294j.fsf@emacs.iotcl.com>
910
cf. <xmqqh5naxwfc.fsf@gitster.g>
911
source: <20260527140820.1438165-1-christian.couder@gmail.com>
@@ -958,19 +922,6 @@ Release tarballs are available at:
922
source: <pull.2281.v13.git.git.1779565714.gitgitgadget@gmail.com>
923
924
961
-* mf/revision-max-count-oldest (2026-06-10) 2 commits
962
- (merged to 'next' on 2026-06-11 at c89a71798a)
963
- + bash-completions: add --max-count-oldest
964
- (merged to 'next' on 2026-06-09 at 076600fa21)
965
- + revision.c: implement --max-count-oldest
966
-
967
- "git rev-list" (and "git log" family of commands) learned a new "--max-count-oldest"
968
- that picks oldest N commits in the range instead of the usual newest.
969
-
970
- Will merge to 'master'.
971
- source: <xmqq4ijm3p2x.fsf@gitster.g>
972
-
973
-
925
* en/ort-harden-against-corrupt-trees (2026-06-13) 5 commits
926
- cache-tree: fix verify_cache() to catch non-adjacent D/F conflicts
927
- merge-ort: abort merge when trees have duplicate entries
@@ -981,7 +932,7 @@ Release tarballs are available at:
932
"ort" merge backend handles merging corrupt trees better by
933
aborting when it should.
934
984
- Waiting for response(s) to review comment(s).
935
+ Will merge to 'next'?
936
cf. <xmqq5x3ldu4h.fsf@gitster.g>
937
source: <pull.2096.v2.git.1781419047.gitgitgadget@gmail.com>
938
@@ -1022,8 +973,8 @@ Release tarballs are available at:
973
appearing falsely related to unrelated commits rendered immediately
974
above them.
975
1025
- Waiting for response(s) to review comment(s).
1026
- cf. <xmqqo6hdepgy.fsf@gitster.g>
976
+ Will merge to 'next'?
977
+ cf. <xmqq8q8e4f3s.fsf@gitster.g>
978
source: <20260613-ps-pre-commit-indent-v5-0-8d308efea63d@gmail.com>
979
980
--------------------------------------------------