What's cooking (2025/03 #05)
Junio C Hamano committed
Mar 18, 2025 at 13:09 UTC
e7c03c335148f78c2dad64f84188c67956ed2768
1 file changed
+276
-85
whats-cooking.txt
+276
-85
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Mar 2025, #04; Fri, 14)
2
+Subject: What's cooking in git.git (Mar 2025, #05; Tue, 18)
3
X-master-at: 683c54c999c301c2cd6f715c411407c413b1d84e
4
-X-next-at: d1b26642dacc169ed6e4a1495e3fa114e8b27faa
4
+X-next-at: e94155a9ecafb89f308d834dea8fed4f7ad85d2a
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Mar 2025, #04; Fri, 14)
7
+What's cooking in git.git (Mar 2025, #05; Tue, 18)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -17,6 +17,12 @@ 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
+Now Git 2.49 is out, we may see some regression reports, in which
21
+case we would have to first deal with them. I'll be on vacation for
22
+a few weeks, and will be back in early April. I may occasionally be
23
+online to merge some topics down but I will generally be much slower
24
+than usual during the latter half of this month.
25
+
26
Copies of the source code to Git live in many repositories, and the
27
following is a list of the ones I push into or their mirrors. Some
28
repositories have only a subset of branches.
@@ -48,48 +54,223 @@ Release tarballs are available at:
54
--------------------------------------------------
55
[New Topics]
56
51
-* en/diff-rename-follow-fix (2025-03-13) 1 commit
52
- - diffcore-rename: fix BUG when break detection and --follow used together
57
+* aj/doc-restore-p-update (2025-03-18) 1 commit
58
+ - doc: restore: remove note on --patch w/ pathspecs
59
54
- A corner-case bug in "git log --follow -B" has been fixed.
60
+ Stale description in "git restore -p" documentation has been
61
+ updated.
62
63
Will merge to 'next'.
57
- source: <pull.1876.git.1741395615315.gitgitgadget@gmail.com>
64
+ source: <pull.1504.v2.git.git.1685654097812.gitgitgadget@gmail.com>
65
+
66
+
67
+* en/random-cleanups (2025-03-17) 5 commits
68
+ (merged to 'next' on 2025-03-18 at 87acd24a85)
69
+ + merge-ort: remove extraneous word in comment
70
+ + merge-ort: fix accidental strset<->strintmap
71
+ + t7615: be more explicit about diff algorithm used
72
+ + t6423: fix a comment that accidentally reversed two commits
73
+ + stash: remove merge-recursive.h include
74
+
75
+ Miscellaneous code clean-ups.
76
+
77
+ Will merge to 'master'.
78
+ source: <pull.1882.git.1742108339.gitgitgadget@gmail.com>
79
+
80
+
81
+* es/meson-building-docs-requires-perl (2025-03-17) 1 commit
82
+ (merged to 'next' on 2025-03-18 at 1c1d88dcb7)
83
+ + meson: fix perl detection when docs are enabled, but perl bindings aren't
84
+
85
+ Build update.
86
+
87
+ Will merge to 'master'.
88
+ source: <20250316060605.166364-1-eschwartz@gentoo.org>
89
+
90
+
91
+* hj/doc-rev-list-ancestry-fix (2025-03-18) 1 commit
92
+ (merged to 'next' on 2025-03-18 at e94155a9ec)
93
+ + doc: add missing commit C to the graph for --ancestry-path=H D..M
94
+
95
+ Doc update.
96
+
97
+ Will merge to 'master'.
98
+ source: <pull.1883.git.1742089659610.gitgitgadget@gmail.com>
99
+
100
+
101
+* ja/doc-branch-markup (2025-03-17) 2 commits
102
+ - doc: apply new format to git-branch man page
103
+ - completion: take into account the formatting backticks for options
104
+
105
+ Expecting a reroll to lose GNUism.
106
+ cf. <2773494.mvXUDI8C0e@cayenne>
107
+ source: <pull.1880.git.1742056310.gitgitgadget@gmail.com>
108
+
109
+
110
+* jc/ci-meson-check-build-docs-fix (2025-03-14) 1 commit
111
+ - install meson for Documentation job
112
+ (this branch uses ps/ci-meson-check-build-docs.)
113
+
114
+ The documentation CI job tries to build test documentation pages
115
+ with both make- and meson-based build procedures, but somehow
116
+ forgot to install meson in the Ci environment, which has been
117
+ corrected.
118
+
119
+ Will discard. Karthik root-caused the issue.
120
+ cf. <xmqqmsdi49h8.fsf_-_@gitster.g>
121
+ cf. <CAOLa=ZRODjYfDXQ8m+hDosV7RBGDWeehzSvsR-+-HCmbS+tAcQ@mail.gmail.com>
122
+ source: <20250314184130.GA578421@coredump.intra.peff.net>
123
+
124
+
125
+* ps/mingw-creat-excl-fix (2025-03-13) 2 commits
126
+ - compat/mingw: fix EACCESS when opening files with `O_CREAT | O_EXCL`
127
+ - compat/mingw: handle O_CLOEXEC in `mingw_open_existing()`
128
+
129
+ Attempt to fix lockfile contention in reftable code on Windows.
130
+
131
+ The second step needs rethinking.
132
+ cf. <Z9g85X8sNqFOwRaU@pks.im>
133
+ source: <20250313-b4-pks-mingw-lockfile-flake-v1-0-bc5d3e70f516@pks.im>
134
+
135
+
136
+* rs/xdiff-context-length-fix (2025-03-14) 1 commit
137
+ (merged to 'next' on 2025-03-18 at aca4b320d2)
138
+ + xdiff: avoid arithmetic overflow in xdl_get_hunk()
139
+
140
+ The xdiff code on 32-bit platform misbehaved when an insanely large
141
+ context size is given, which has been corrected.
142
+
143
+ Will merge to 'master'.
144
+ source: <4e9b6b4c-aaa1-4c6f-93f4-7bb04607e843@web.de>
145
+
146
+
147
+* sj/meson-test-environ-fix (2025-03-14) 1 commit
148
+ - meson: use test_environment conditionally.
149
+
150
+ meson-based build procedure was overly aggressive in using test
151
+ environment in two contrib/ directories, which was corrected.
152
+
153
+ Needs review.
154
+ source: <3d127f293818f935efdb9ca7bb556e6a8f233ef7.1741975557.git.sam@gentoo.org>
155
+
156
+
157
+* tb/combine-cruft-below-size (2025-03-17) 6 commits
158
+ - repack: begin combining cruft packs with `--combine-cruft-below-size`
159
+ - repack: avoid combining cruft packs with `--max-cruft-size`
160
+ - t/t7704-repack-cruft.sh: consolidate `write_blob()`
161
+ - t/t7704-repack-cruft.sh: clarify wording in --max-cruft-size tests
162
+ - t/t5329-pack-objects-cruft.sh: evict 'repack'-related tests
163
+ - Merge branch 'tb/multi-cruft-pack-refresh-fix' into tb/combine-cruft-below-size
164
+ (this branch uses tb/multi-cruft-pack-refresh-fix.)
165
+
166
+ "git repack" learned "--combine-cruft-below-size" option that
167
+ controls how cruft-packs are combined.
168
+
169
+ Needs review.
170
+ source: <cover.1742252411.git.me@ttaylorr.com>
171
+
172
+
173
+* jh/hash-init-fixes (2025-03-18) 1 commit
174
+ - index-pack, unpack-objects: restore missing ->init_fn
175
+
176
+ An earlier code refactoring of the hash machinery missed a few
177
+ required calls to init_fn.
178
+
179
+ Needs review.
180
+ source: <20250318111616.113941-1-hmz007@gmail.com>
181
+
182
+
183
+* jk/fetch-follow-remote-head-fix (2025-03-18) 3 commits
184
+ - fetch: don't ask for remote HEAD if followRemoteHEAD is "never"
185
+ - fetch: only respect followRemoteHEAD with configured refspecs
186
+ - Merge branch 'jk/fetch-ref-prefix-cleanup' into jk/fetch-follow-remote-head-fix
187
+ (this branch uses jk/fetch-ref-prefix-cleanup.)
188
+
189
+ "git fetch [<remote>]" with only the configured fetch refspec
190
+ should be the only thing to update refs/remotes/<remote>/HEAD,
191
+ but the code was overly eager to do so in other cases.
192
+
193
+ Will merge to 'next'?
194
+ source: <20250318053905.GA2051217@coredump.intra.peff.net>
195
+
196
+
197
+* pw/build-breaking-changes-doc (2025-03-18) 1 commit
198
+ - docs: add BreakingChanges to TECH_DOCS target
199
+
200
+ A documentation page was left out from formatting and installation,
201
+ which has been corrected.
202
+
203
+ Will merge to 'next'.
204
+ source: <pull.1921.git.git.1742308900290.gitgitgadget@gmail.com>
205
+
206
+
207
+* pw/doc-pack-refs-markup-fix (2025-03-18) 1 commit
208
+ - pack-refs doc: fix indentation for --exclude
209
+
210
+ Doc markup fix.
211
+
212
+ Will merge to 'next'.
213
+ source: <pull.1920.git.git.1742308828163.gitgitgadget@gmail.com>
214
+
215
+
216
+* sc/bundle-uri-use-all-refs-in-bundle (2025-03-18) 2 commits
217
+ - bundle-uri: add test for bundle-uri clones with tags
218
+ - bundle-uri: copy all bundle references ino the refs/bundle space
219
+
220
+ Bundle-URI feature did not use refs recorded in the bundle other
221
+ than normal branches as anchoring points to optimize the follow-up
222
+ fetch during "git clone"; now it is told to utilize all.
223
+
224
+ Comments?
225
+ source: <pull.1897.v3.git.git.1742312173.gitgitgadget@gmail.com>
226
227
--------------------------------------------------
228
[Cooking]
229
62
-* en/merge-ort-prepare-to-remove-recursive (2025-03-13) 6 commits
63
- - am: switch from merge_recursive_generic() to merge_ort_generic()
64
- - merge-ort: fix merge.directoryRenames=false
65
- - t3650: document bug when directory renames are turned off
66
- - merge-ort: support having merge verbosity be set to 0
67
- - merge-ort: allow rename detection to be disabled
68
- - merge-ort: add new merge_ort_generic() function
230
+* en/diff-rename-follow-fix (2025-03-14) 1 commit
231
+ (merged to 'next' on 2025-03-18 at 56808a7eda)
232
+ + diffcore-rename: fix BUG when break detection and --follow used together
233
+
234
+ A corner-case bug in "git log --follow -B" has been fixed.
235
+
236
+ Will merge to 'master'.
237
+ source: <pull.1876.v2.git.1742000894041.gitgitgadget@gmail.com>
238
+
239
+
240
+* en/merge-ort-prepare-to-remove-recursive (2025-03-18) 6 commits
241
+ (merged to 'next' on 2025-03-18 at a911944a1c)
242
+ + am: switch from merge_recursive_generic() to merge_ort_generic()
243
+ + merge-ort: fix merge.directoryRenames=false
244
+ + t3650: document bug when directory renames are turned off
245
+ + merge-ort: support having merge verbosity be set to 0
246
+ + merge-ort: allow rename detection to be disabled
247
+ + merge-ort: add new merge_ort_generic() function
248
249
First step of deprecating and removing merge-recursive.
250
72
- Will merge to 'next'.
251
+ Will merge to 'master'.
252
source: <pull.1875.v2.git.1741834001.gitgitgadget@gmail.com>
253
254
76
-* jk/use-wunreachable-code-for-devs (2025-03-07) 1 commit
77
- (merged to 'next' on 2025-03-07 at b5c54fea6a)
255
+* jk/use-wunreachable-code-for-devs (2025-03-17) 3 commits
256
+ (merged to 'next' on 2025-03-18 at fe32168eef)
257
+ config.mak.dev: enable -Wunreachable-code
258
+ + git-compat-util: add NOT_CONSTANT macro and use it in atfork_prepare()
259
+ + run-command: use errno to check for sigfillset() error
260
261
Enable -Wunreachable-code for developer builds.
262
82
- Reverted out of 'next', as macOS CI job stops with a false positive.
83
- cf. <20250310160440.GA26189@coredump.intra.peff.net>
84
- source: <20250307225444.GA42758@coredump.intra.peff.net>
263
+ Will merge to 'master'.
264
+ source: <20250317235329.809302-1-gitster@pobox.com>
265
266
267
* ab/decorate-code-cleanup (2025-03-10) 1 commit
88
- - decorate: fix sign comparison warnings
268
+ (merged to 'next' on 2025-03-18 at 7ede1484eb)
269
+ + decorate: fix sign comparison warnings
270
271
Code clean-up.
272
92
- Will merge to 'next'.
273
+ Will merge to 'master'.
274
source: <7c219279-8151-49c0-8fc0-8abe2624aca9@gmail.com>
275
276
@@ -119,7 +300,7 @@ Release tarballs are available at:
300
301
Doc markup updates.
302
122
- Will cook in 'next'.
303
+ Will merge to 'master'.
304
source: <pull.1878.git.1741549511665.gitgitgadget@gmail.com>
305
306
@@ -140,22 +321,24 @@ Release tarballs are available at:
321
322
323
* jk/fetch-ref-prefix-cleanup (2025-03-10) 9 commits
143
- - fetch: use ref prefix list to skip ls-refs
144
- - fetch: avoid ls-refs only to ask for HEAD symref update
145
- - fetch: stop protecting additions to ref-prefix list
146
- - fetch: ask server to advertise HEAD for config-less fetch
147
- - refspec_ref_prefixes(): clean up refspec_item logic
148
- - t5516: beef up exact-oid ref prefixes test
149
- - t5516: drop NEEDSWORK about v2 reachability behavior
150
- - t5516: prefer "oid" to "sha1" in some test titles
151
- - t5702: fix typo in test name
324
+ (merged to 'next' on 2025-03-18 at ab3e5cf19f)
325
+ + fetch: use ref prefix list to skip ls-refs
326
+ + fetch: avoid ls-refs only to ask for HEAD symref update
327
+ + fetch: stop protecting additions to ref-prefix list
328
+ + fetch: ask server to advertise HEAD for config-less fetch
329
+ + refspec_ref_prefixes(): clean up refspec_item logic
330
+ + t5516: beef up exact-oid ref prefixes test
331
+ + t5516: drop NEEDSWORK about v2 reachability behavior
332
+ + t5516: prefer "oid" to "sha1" in some test titles
333
+ + t5702: fix typo in test name
334
+ (this branch is used by jk/fetch-follow-remote-head-fix.)
335
336
In protocol v2 where the refs advertisement is constrained, we try
337
to tell the server side not to limit the advertisement when there
338
is no specific need to, which has been the source of confusion and
339
recent bugs. Revamp the logic to simplify.
340
158
- Will merge to 'next'.
341
+ Will merge to 'master'.
342
source: <20250309030101.GA2334064@coredump.intra.peff.net>
343
344
@@ -174,51 +357,58 @@ Release tarballs are available at:
357
source: <20250313001706.3390502-1-jltobler@gmail.com>
358
359
177
-* kn/reflog-drop (2025-03-10) 1 commit
360
+* kn/reflog-drop (2025-03-17) 2 commits
361
- reflog: implement subcommand to drop reflogs
362
+ - reflog: improve error for when reflog is not found
363
364
"git reflog" learns "drop" subcommand, that discards the entire
365
reflog data for a ref.
366
367
Will merge to 'next'?
184
- source: <20250310-493-add-command-to-purge-reflog-entries-v2-1-05caa92e0bfa@gmail.com>
368
+ source: <20250314-493-add-command-to-purge-reflog-entries-v3-0-c24e23a6146d@gmail.com>
369
370
371
* am/dir-dedup-decl-of-repository (2025-03-11) 1 commit
188
- - dir.h: remove duplicate forward declaration of struct repository
372
+ (merged to 'next' on 2025-03-18 at 9075454132)
373
+ + dir.h: remove duplicate forward declaration of struct repository
374
375
Code cleanup.
376
192
- Will merge to 'next'.
377
+ Will merge to 'master'.
378
source: <pull.1879.git.1741705175922.gitgitgadget@gmail.com>
379
380
196
-* cc/lop-remote (2025-03-13) 1 commit
381
+* cc/lop-remote (2025-03-18) 4 commits
382
+ - promisor-remote: compare remote names case sensitively
383
+ - promisor-remote: fix possible issue when no URL is advertised
384
- promisor-remote: fix segfault when remote URL is missing
385
+ - t5710: arrange to delete the client before cloning
386
387
Bugfix in newly introduced large-object-promisor remote support.
388
201
- Will merge to 'next'?
202
- source: <20250313103859.817127-1-christian.couder@gmail.com>
389
+ Will merge to 'next'.
390
+ source: <20250318110008.656695-1-christian.couder@gmail.com>
391
392
393
* ps/ci-meson-check-build-docs (2025-03-12) 1 commit
394
- ci: perform build and smoke tests for Meson docs
395
+ (this branch is used by jc/ci-meson-check-build-docs-fix.)
396
397
CI update.
398
210
- Will merge to 'next'.
399
+ On hold waiting for the fix-up to settle.
400
source: <20250312-b4-pks-ci-meson-docs-v1-1-5e7cf7ac959a@pks.im>
401
402
403
* ps/meson-with-breaking-changes (2025-03-12) 3 commits
215
- - meson: don't install git-pack-redundant(1) docs with breaking changes
216
- - meson: don't compile git-pack-redundant(1) with breaking changes
217
- - meson: define WITH_BREAKING_CHANGES when enabling breaking changes
404
+ (merged to 'next' on 2025-03-18 at 15b1c62eff)
405
+ + meson: don't install git-pack-redundant(1) docs with breaking changes
406
+ + meson: don't compile git-pack-redundant(1) with breaking changes
407
+ + meson: define WITH_BREAKING_CHANGES when enabling breaking changes
408
409
Update meson based build procedure for breaking changes support.
410
221
- Will merge to 'next'.
411
+ Will merge to 'master'.
412
source: <20250312-b4-pks-meson-breaking-changes-v1-0-b89e9a59d228@pks.im>
413
414
@@ -240,7 +430,7 @@ Release tarballs are available at:
430
source: <20250304113323.10564-1-kuforiji98@gmail.com>
431
432
243
-* dm/completion-remote-names-fix (2025-03-05) 2 commits
433
+* dm/completion-remote-names-fix (2025-03-18) 2 commits
434
- completion: fix bugs with slashes in remote names
435
- completion: add helper to count path components
436
@@ -248,8 +438,8 @@ Release tarballs are available at:
438
updated to cope with remote repository nicknames with slashes in
439
them.
440
251
- Comments?
252
- source: <d5860dbe1e6a149d72739af3271369b3@mandelberg.org>
441
+ Will merge to 'next'.
442
+ source: <1587533591c81d38977e62165784f8eb@mandelberg.org>
443
444
445
* tb/refs-exclude-fixes (2025-03-06) 2 commits
@@ -261,7 +451,7 @@ Release tarballs are available at:
451
broken for some time, which confused upload-pack to advertise
452
different set of refs. This has been corrected.
453
264
- Will cook in 'next'.
454
+ Will merge to 'master'.
455
source: <cover.1741275245.git.me@ttaylorr.com>
456
457
@@ -273,7 +463,7 @@ Release tarballs are available at:
463
The merge-recursive and merge-ort machinery crashed in corner cases
464
when certain renames are involved.
465
276
- Will cook in 'next'.
466
+ Will merge to 'master'.
467
source: <pull.1873.git.1741275027.gitgitgadget@gmail.com>
468
469
@@ -335,7 +525,7 @@ Release tarballs are available at:
525
to use the repository instance supplied by git.c:run_builtin(), its
526
caller.
527
338
- Will cook in 'next'.
528
+ Will merge to 'master'.
529
source: <20250307233543.1721552-1-usmanakinyemi202@gmail.com>
530
531
@@ -354,39 +544,42 @@ Release tarballs are available at:
544
545
546
* ps/refname-avail-check-optim (2025-03-12) 16 commits
357
- - refs: reuse iterators when determining refname availability
358
- - refs/iterator: implement seeking for files iterators
359
- - refs/iterator: implement seeking for packed-ref iterators
360
- - refs/iterator: implement seeking for ref-cache iterators
361
- - refs/iterator: implement seeking for reftable iterators
362
- - refs/iterator: implement seeking for merged iterators
363
- - refs/iterator: provide infrastructure to re-seek iterators
364
- - refs/iterator: separate lifecycle from iteration
365
- - refs: stop re-verifying common prefixes for availability
366
- - refs/files: batch refname availability checks for initial transactions
367
- - refs/files: batch refname availability checks for normal transactions
368
- - refs/reftable: batch refname availability checks
369
- - refs: introduce function to batch refname availability checks
370
- - builtin/update-ref: skip ambiguity checks when parsing object IDs
371
- - object-name: allow skipping ambiguity checks in `get_oid()` family
372
- - object-name: introduce `repo_get_oid_with_flags()`
547
+ (merged to 'next' on 2025-03-18 at 726197f7e0)
548
+ + refs: reuse iterators when determining refname availability
549
+ + refs/iterator: implement seeking for files iterators
550
+ + refs/iterator: implement seeking for packed-ref iterators
551
+ + refs/iterator: implement seeking for ref-cache iterators
552
+ + refs/iterator: implement seeking for reftable iterators
553
+ + refs/iterator: implement seeking for merged iterators
554
+ + refs/iterator: provide infrastructure to re-seek iterators
555
+ + refs/iterator: separate lifecycle from iteration
556
+ + refs: stop re-verifying common prefixes for availability
557
+ + refs/files: batch refname availability checks for initial transactions
558
+ + refs/files: batch refname availability checks for normal transactions
559
+ + refs/reftable: batch refname availability checks
560
+ + refs: introduce function to batch refname availability checks
561
+ + builtin/update-ref: skip ambiguity checks when parsing object IDs
562
+ + object-name: allow skipping ambiguity checks in `get_oid()` family
563
+ + object-name: introduce `repo_get_oid_with_flags()`
564
(this branch is used by kn/non-transactional-batch-updates.)
565
566
The code paths to check whether a refname X is available (by seeing
567
if another ref X/Y exists, etc.) have been optimized.
568
378
- Will merge to 'next'.
569
+ Will merge to 'master'.
570
source: <20250312-pks-update-ref-optimization-v6-0-f778e0414f55@pks.im>
571
572
573
* tb/multi-cruft-pack-refresh-fix (2025-03-13) 1 commit
383
- - builtin/pack-objects.c: freshen objects from existing cruft packs
574
+ (merged to 'next' on 2025-03-18 at e3f090e427)
575
+ + builtin/pack-objects.c: freshen objects from existing cruft packs
576
+ (this branch is used by tb/combine-cruft-below-size.)
577
578
Certain "cruft" objects would have never been refreshed when there
579
are multiple cruft packs in the repository, which has been
580
corrected.
581
389
- Will merge to 'next'.
582
+ Will merge to 'master'.
583
source: <1563552bbda0bc910c9f41b0fabc3225c4d778fc.1741889018.git.me@ttaylorr.com>
584
585
@@ -410,17 +603,18 @@ Release tarballs are available at:
603
604
605
* cc/signed-fast-export-import (2025-03-10) 6 commits
413
- - fast-export, fast-import: add support for signed-commits
414
- - fast-export: do not modify memory from get_commit_buffer
415
- - git-fast-export.adoc: clarify why 'verbatim' may not be a good idea
416
- - fast-export: rename --signed-tags='warn' to 'warn-verbatim'
417
- - fast-export: fix missing whitespace after switch
418
- - git-fast-import.adoc: add missing LF in the BNF
606
+ (merged to 'next' on 2025-03-18 at d98973e2cb)
607
+ + fast-export, fast-import: add support for signed-commits
608
+ + fast-export: do not modify memory from get_commit_buffer
609
+ + git-fast-export.adoc: clarify why 'verbatim' may not be a good idea
610
+ + fast-export: rename --signed-tags='warn' to 'warn-verbatim'
611
+ + fast-export: fix missing whitespace after switch
612
+ + git-fast-import.adoc: add missing LF in the BNF
613
614
"git fast-export | git fast-import" learns to deal with commit and
615
tag objects with embedded signatures a bit better.
616
423
- Will merge to 'next'.
617
+ Will merge to 'master'.
618
cf. <CABPp-BGyA8iBA0BFO8FcpZAMca94aVu2vHHRi4Oz=nCWxJSDPg@mail.gmail.com>
619
source: <20250310155746.879481-1-christian.couder@gmail.com>
620
@@ -435,7 +629,7 @@ Release tarballs are available at:
629
A post-processing filter for "diff --raw" output has been
630
introduced.
631
438
- Will cook in 'next'.
632
+ Will merge to 'master'.
633
source: <20250228213346.1335224-1-jltobler@gmail.com>
634
635
@@ -512,7 +706,7 @@ Release tarballs are available at:
706
707
"git fsck" becomes more careful when checking the refs.
708
515
- Will cook in 'next'.
709
+ Will merge to 'master'.
710
source: <Z8CMx7O19PMs9sVY@ArchLinux>
711
712
@@ -528,7 +722,7 @@ Release tarballs are available at:
722
source: <xmqq5xnladwi.fsf@gitster.g>
723
724
531
-* tb/incremental-midx-part-2 (2024-11-20) 15 commits
725
+* tb/incremental-midx-part-2 (2025-03-14) 13 commits
726
- midx: implement writing incremental MIDX bitmaps
727
- pack-bitmap.c: use `ewah_or_iterator` for type bitmap iterators
728
- pack-bitmap.c: keep track of each layer's type bitmaps
@@ -542,14 +736,11 @@ Release tarballs are available at:
736
- pack-bitmap.c: open and store incremental bitmap layers
737
- pack-revindex: prepare for incremental MIDX bitmaps
738
- Documentation: describe incremental MIDX bitmaps
545
- - Merge branch 'tb/pseudo-merge-bitmap-fixes' into tb/incremental-midx-part-2
546
- - Merge branch 'tb/incremental-midx-part-1' into tb/incremental-midx-part-2
739
740
Incrementally updating multi-pack index files.
741
550
- Expecting a (hopefully minor and final) reroll.
551
- cf. <Z8JSreTnEFlocYQ9@nand.local> <Z8JLbxBQh7XUpplz@nand.local>
552
- source: <cover.1732054032.git.me@ttaylorr.com>
742
+ Will merge to 'next'.
743
+ source: <cover.1741983492.git.me@ttaylorr.com>
744
745
746
* ej/cat-file-remote-object-info (2025-02-24) 8 commits