What's cooking (2022/08 #05)
Junio C Hamano committed
Aug 15, 2022 at 13:15 UTC
59d992158534c8291f548563a9c949dae4ad7796
1 file changed
+216
-179
whats-cooking.txt
+216
-179
@@ -1,9 +1,9 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Aug 2022, #04; Thu, 11)
3
-X-master-at: 5502f77b6944eda8e26813d8f542cffe7d110aea
4
-X-next-at: 219fe53025fdf5c3fb79d289a36eb2cad3f38a04
2
+Subject: What's cooking in git.git (Aug 2022, #05; Mon, 15)
3
+X-master-at: 9bf691b78cf906751e65d65ba0c6ffdcd9a5a12c
4
+X-next-at: c19287026c9b940f7f43d34e6dacbd5c34e4a2e0
5
6
-What's cooking in git.git (Aug 2022, #04; Thu, 11)
6
+What's cooking in git.git (Aug 2022, #05; Mon, 15)
7
--------------------------------------------------
8
9
Here are the topics that have been cooking in my tree. Commits
@@ -13,14 +13,8 @@ release). Commits prefixed with '-' are only in 'seen', and aren't
13
considered "accepted" at all. A topic without enough support may be
14
discarded after a long period of no activity.
15
16
-A maintenance release, Git 2.37.2, has been tagged. There wasn't
17
-any reason why it had to be done on this day, and there isn't any
18
-security-sensitive fixes in there, but as we have accumulated a few
19
-fixes on the 'master' front, it was a good time to flush them down
20
-to the maintenance track. Those who are running 'master' or better
21
-have been running with all these fixes for more than a week and do
22
-not have to worry about it. We are in the week #5 of a 12-week
23
-cycle (cf. https://tinyurl.com/gitCal).
16
+We are at the beginning of the week #6 of a 12-week cycle (cf.
17
+https://tinyurl.com/gitCal).
18
19
Copies of the source code to Git live in many repositories, and the
20
following is a list of the ones I push into or their mirrors. Some
@@ -50,9 +44,185 @@ Release tarballs are available at:
44
45
https://www.kernel.org/pub/software/scm/git/
46
47
+--------------------------------------------------
48
+[Graduated to 'master']
49
+
50
+* ab/hooks-regression-fix (2022-08-05) 1 commit
51
+ (merged to 'next' on 2022-08-08 at f5a3f88983)
52
+ + hook API: don't segfault on strbuf_addf() to NULL "out"
53
+
54
+ A follow-up fix to a fix for a regression in 2.36.
55
+ source: <patch-1.1-2450e3e65cf-20220805T141402Z-avarab@gmail.com>
56
+
57
+
58
+* ab/leak-check (2022-07-27) 15 commits
59
+ (merged to 'next' on 2022-08-05 at 2a6b9c8432)
60
+ + CI: use "GIT_TEST_SANITIZE_LEAK_LOG=true" in linux-leaks
61
+ + upload-pack: fix a memory leak in create_pack_file()
62
+ + leak tests: mark passing SANITIZE=leak tests as leak-free
63
+ + leak tests: don't skip some tests under SANITIZE=leak
64
+ + test-lib: have the "check" mode for SANITIZE=leak consider leak logs
65
+ + test-lib: add a GIT_TEST_PASSING_SANITIZE_LEAK=check mode
66
+ + test-lib: simplify by removing test_external
67
+ + tests: move copy/pasted PERL + Test::More checks to a lib-perl.sh
68
+ + t/Makefile: don't remove test-results in "clean-except-prove-cache"
69
+ + test-lib: add a SANITIZE=leak logging mode
70
+ + t/README: reword the "GIT_TEST_PASSING_SANITIZE_LEAK" description
71
+ + test-lib: add a --invert-exit-code switch
72
+ + test-lib: fix GIT_EXIT_OK logic errors, use BAIL_OUT
73
+ + test-lib: don't set GIT_EXIT_OK before calling test_atexit_handler
74
+ + test-lib: use $1, not $@ in test_known_broken_{ok,failure}_
75
+
76
+ Extend SANITIZE=leak checking and declare more tests "currently leak-free".
77
+ source: <cover-v3-00.15-00000000000-20220727T230800Z-avarab@gmail.com>
78
+
79
+
80
+* ab/plug-revisions-leak (2022-08-03) 6 commits
81
+ (merged to 'next' on 2022-08-05 at d1ca88976f)
82
+ + revisions API: don't leak memory on argv elements that need free()-ing
83
+ + bisect.c: partially fix bisect_rev_setup() memory leak
84
+ + log: refactor "rev.pending" code in cmd_show()
85
+ + log: fix a memory leak in "git show <revision>..."
86
+ + test-fast-rebase helper: use release_revisions() (again)
87
+ + bisect.c: add missing "goto" for release_revisions()
88
+
89
+ Plug a bit more leaks in the revisions API.
90
+ source: <cover-v3-0.6-00000000000-20220802T152925Z-avarab@gmail.com>
91
+
92
+
93
+* ab/tech-docs-to-help (2022-08-04) 12 commits
94
+ (merged to 'next' on 2022-08-08 at 65c9ec7308)
95
+ + docs: move http-protocol docs to man section 5
96
+ + docs: move cruft pack docs to gitformat-pack
97
+ + docs: move pack format docs to man section 5
98
+ + docs: move signature docs to man section 5
99
+ + docs: move index format docs to man section 5
100
+ + docs: move protocol-related docs to man section 5
101
+ + docs: move commit-graph format docs to man section 5
102
+ + git docs: add a category for file formats, protocols and interfaces
103
+ + git docs: add a category for user-facing file, repo and command UX
104
+ + git help doc: use "<doc>" instead of "<guide>"
105
+ + help.c: remove common category behavior from drop_prefix() behavior
106
+ + help.c: refactor drop_prefix() to use a "switch" statement"
107
+
108
+ Expose a lot of "tech docs" via "git help" interface.
109
+ source: <cover-v8-00.12-00000000000-20220804T162138Z-avarab@gmail.com>
110
+
111
+
112
+* gc/git-reflog-doc-markup (2022-08-01) 1 commit
113
+ (merged to 'next' on 2022-08-05 at f2d8721ab2)
114
+ + Documentation/git-reflog: remove unneeded \ from \{
115
+
116
+ Doc mark-up fix.
117
+ source: <pull.1304.git.git.1659387885711.gitgitgadget@gmail.com>
118
+
119
+
120
+* jc/rerere-autoupdate-doc (2022-08-03) 2 commits
121
+ (merged to 'next' on 2022-08-08 at 6407091d13)
122
+ + doc: clarify rerere-autoupdate
123
+ + doc: consolidate --rerere-autoupdate description
124
+
125
+ Update documentation on the "--[no-]rerere-autoupdate" option.
126
+ source: <xmqq35f2ysd9.fsf@gitster.g>
127
+
128
+
129
+* js/safe-directory-plus (2022-08-08) 5 commits
130
+ (merged to 'next' on 2022-08-10 at 3d32a87210)
131
+ + mingw: handle a file owned by the Administrators group correctly
132
+ + mingw: be more informative when ownership check fails on FAT32
133
+ + mingw: provide details about unsafe directories' ownership
134
+ + setup: prepare for more detailed "dubious ownership" messages
135
+ + setup: fix some formatting
136
+
137
+ Platform-specific code that determines if a directory is OK to use
138
+ as a repository has been taught to report more details, especially
139
+ on Windows.
140
+ source: <pull.1286.v2.git.1659965270.gitgitgadget@gmail.com>
141
+
142
+
143
+* lt/symbolic-ref-sanity (2022-08-01) 1 commit
144
+ (merged to 'next' on 2022-08-03 at 443647b94a)
145
+ + symbolic-ref: refuse to set syntactically invalid target
146
+
147
+ "git symbolic-ref symref non..sen..se" is now diagnosed as an error.
148
+ source: <YugYNzQYWqDCmOqN@coredump.intra.peff.net>
149
+
150
+
151
+* pw/use-glibc-tunable-for-malloc-optim (2022-08-04) 1 commit
152
+ (merged to 'next' on 2022-08-08 at 1300f84dc4)
153
+ + tests: cache glibc version check
154
+
155
+ Avoid repeatedly running getconf to ask libc version in the test
156
+ suite, and instead just as it once per script.
157
+ source: <pull.1311.git.1659620305757.gitgitgadget@gmail.com>
158
+
159
--------------------------------------------------
160
[New Topics]
161
162
+* ll/disk-usage-humanise (2022-08-11) 1 commit
163
+ (merged to 'next' on 2022-08-14 at 3873a83f90)
164
+ + rev-list: support human-readable output for `--disk-usage`
165
+
166
+ "git rev-list --disk-usage" learned to take an optional value
167
+ "human" to show the reported value in human-readable format, like
168
+ "3.40MiB".
169
+
170
+ Will merge to 'master'.
171
+ source: <pull.1313.v5.git.1660193274336.gitgitgadget@gmail.com>
172
+
173
+
174
+* ed/fsmonitor-on-network-disk (2022-08-11) 1 commit
175
+ (merged to 'next' on 2022-08-14 at 637d458d9c)
176
+ + fsmonitor: option to allow fsmonitor to run against network-mounted repos
177
+
178
+ The built-in fsmonitor refuses to work on a network mounted
179
+ repositories; a configuration knob for users to override this has
180
+ been introduced.
181
+
182
+ Will merge to 'master'.
183
+ source: <pull.1317.v4.git.1660262231357.gitgitgadget@gmail.com>
184
+
185
+
186
+* jk/is-promisor-object-keep-tree-in-use (2022-08-14) 1 commit
187
+ - is_promisor_object(): fix use-after-free of tree buffer
188
+
189
+ An earlier optimization discarded a tree-object buffer that is
190
+ still in use, which has been corrected.
191
+
192
+ Will merge to 'next'.
193
+ source: <YviWO9Bhz5PU1HaL@coredump.intra.peff.net>
194
+
195
+
196
+* js/fetch-negotiation-trace (2022-08-15) 1 commit
197
+ - fetch-pack: add tracing for negotiation rounds
198
+
199
+ The common ancestor negotiation exchange during a "git fetch"
200
+ session now leaves trace log.
201
+
202
+ Will merge to 'next'.
203
+ source: <4390677ec75d51487142adf7c2ab821cbd24a53e.1659477669.git.steadmon@google.com>
204
+
205
+
206
+* pw/rebase-keep-base-fixes (2022-08-15) 5 commits
207
+ - rebase --keep-base: imply --no-fork-point
208
+ - rebase --keep-base: imply --reapply-cherry-picks
209
+ - rebase: factor out merge_base calculation
210
+ - rebase: store orig_head as a commit
211
+ - t3416: set $EDITOR in subshell
212
+
213
+ "git rebase --keep-base" used to discard the commits that are
214
+ already cherry-picked to the upstream, even when "keep-base" meant
215
+ that the base, on top of which the history is being rebuilt, does
216
+ not yet include these cherry-picked commits. The --keep-base
217
+ option now implies --reapply-cherry-picks and --no-fork-point
218
+ options.
219
+
220
+ Needs review.
221
+ source: <pull.1323.git.1660576283.gitgitgadget@gmail.com>
222
+
223
+--------------------------------------------------
224
+[Cooking]
225
+
226
* fc/vimdiff-layout-vimdiff3-fix (2022-08-10) 7 commits
227
(merged to 'next' on 2022-08-11 at a14fec292f)
228
+ mergetools: vimdiff: simplify tabfirst
@@ -105,8 +275,6 @@ Release tarballs are available at:
275
An attempt to rewrite remaining merge strategies from shell to C.
276
source: <20220809185429.20098-1-alban.gruin@gmail.com>
277
108
---------------------------------------------------
109
-[Cooking]
278
279
* sy/mv-out-of-cone (2022-08-10) 9 commits
280
- mv: check overwrite for in-to-out move
@@ -128,30 +296,21 @@ Release tarballs are available at:
296
297
298
* sy/sparse-rm (2022-08-08) 5 commits
131
- - rm: integrate with sparse-index
132
- - rm: expand the index only when necessary
133
- - pathspec.h: move pathspec_needs_expanded_index() from reset.c to here
134
- - t1092: add tests for `git-rm`
135
- - Merge branch 'vd/sparse-reset-checkout-fixes' into sy/sparse-rm
299
+ (merged to 'next' on 2022-08-12 at 5bf10965fb)
300
+ + rm: integrate with sparse-index
301
+ + rm: expand the index only when necessary
302
+ + pathspec.h: move pathspec_needs_expanded_index() from reset.c to here
303
+ + t1092: add tests for `git-rm`
304
+ + Merge branch 'vd/sparse-reset-checkout-fixes' into sy/sparse-rm
305
(this branch uses vd/sparse-reset-checkout-fixes.)
306
307
"git rm" has become more aware of the sparse-index feature.
308
140
- Will merge to 'next'?
141
- source: <20220807041335.1790658-1-shaoxuan.yuan02@gmail.com>
142
-
143
-
144
-* lt/symbolic-ref-sanity (2022-08-01) 1 commit
145
- (merged to 'next' on 2022-08-03 at 443647b94a)
146
- + symbolic-ref: refuse to set syntactically invalid target
147
-
148
- "git symbolic-ref symref non..sen..se" is now diagnosed as an error.
149
-
309
Will merge to 'master'.
151
- source: <YugYNzQYWqDCmOqN@coredump.intra.peff.net>
310
+ source: <20220807041335.1790658-1-shaoxuan.yuan02@gmail.com>
311
312
154
-* vd/scalar-generalize-diagnose (2022-08-10) 11 commits
313
+* vd/scalar-generalize-diagnose (2022-08-12) 11 commits
314
- scalar: update technical doc roadmap
315
- scalar-diagnose: use 'git diagnose --mode=all'
316
- builtin/bugreport.c: create '--diagnose' option
@@ -169,17 +328,7 @@ Release tarballs are available at:
328
"git bugreport".
329
330
Will merge to 'next'?
172
- source: <pull.1310.v3.git.1660174473.gitgitgadget@gmail.com>
173
-
174
-
175
-* gc/git-reflog-doc-markup (2022-08-01) 1 commit
176
- (merged to 'next' on 2022-08-05 at f2d8721ab2)
177
- + Documentation/git-reflog: remove unneeded \ from \{
178
-
179
- Doc mark-up fix.
180
-
181
- Will merge to 'master'.
182
- source: <pull.1304.git.git.1659387885711.gitgitgadget@gmail.com>
331
+ source: <pull.1310.v4.git.1660335019.gitgitgadget@gmail.com>
332
333
334
* jk/pipe-command-nonblock (2022-08-03) 1 commit
@@ -195,32 +344,6 @@ Release tarballs are available at:
344
source: <YunxHOa2sJeEpJxd@coredump.intra.peff.net>
345
346
198
-* ab/plug-revisions-leak (2022-08-03) 6 commits
199
- (merged to 'next' on 2022-08-05 at d1ca88976f)
200
- + revisions API: don't leak memory on argv elements that need free()-ing
201
- + bisect.c: partially fix bisect_rev_setup() memory leak
202
- + log: refactor "rev.pending" code in cmd_show()
203
- + log: fix a memory leak in "git show <revision>..."
204
- + test-fast-rebase helper: use release_revisions() (again)
205
- + bisect.c: add missing "goto" for release_revisions()
206
-
207
- Plug a bit more leaks in the revisions API.
208
-
209
- Will merge to 'master'.
210
- source: <cover-v3-0.6-00000000000-20220802T152925Z-avarab@gmail.com>
211
-
212
-
213
-* jc/rerere-autoupdate-doc (2022-08-03) 2 commits
214
- (merged to 'next' on 2022-08-08 at 6407091d13)
215
- + doc: clarify rerere-autoupdate
216
- + doc: consolidate --rerere-autoupdate description
217
-
218
- Update documentation on the "--[no-]rerere-autoupdate" option.
219
-
220
- Will merge to 'master'.
221
- source: <xmqq35f2ysd9.fsf@gitster.g>
222
-
223
-
347
* es/mark-gc-cruft-as-experimental (2022-08-03) 2 commits
348
- config: let feature.experimental imply gc.cruftPacks=true
349
- gc: add tests for --cruft and friends
@@ -234,60 +357,19 @@ Release tarballs are available at:
357
source: <20220803205721.3686361-1-emilyshaffer@google.com>
358
359
237
-* pw/use-glibc-tunable-for-malloc-optim (2022-08-04) 1 commit
238
- (merged to 'next' on 2022-08-08 at 1300f84dc4)
239
- + tests: cache glibc version check
240
-
241
- Avoid repeatedly running getconf to ask libc version in the test
242
- suite, and instead just as it once per script.
243
-
244
- Will merge to 'master'.
245
- source: <pull.1311.git.1659620305757.gitgitgadget@gmail.com>
246
-
247
-
360
* vd/sparse-reset-checkout-fixes (2022-08-08) 4 commits
249
- - unpack-trees: unpack new trees as sparse directories
250
- - cache.h: create 'index_name_pos_sparse()'
251
- - oneway_diff: handle removed sparse directories
252
- - checkout: fix nested sparse directory diff in sparse index
361
+ (merged to 'next' on 2022-08-12 at 755d6ecdb8)
362
+ + unpack-trees: unpack new trees as sparse directories
363
+ + cache.h: create 'index_name_pos_sparse()'
364
+ + oneway_diff: handle removed sparse directories
365
+ + checkout: fix nested sparse directory diff in sparse index
366
(this branch is used by sy/sparse-rm.)
367
368
Fixes to sparse index compatibility work for "reset" and "checkout"
369
commands.
370
258
- Will merge to 'next'?
259
- source: <pull.1312.v3.git.1659985672.gitgitgadget@gmail.com>
260
-
261
-
262
-* ab/hooks-regression-fix (2022-08-05) 1 commit
263
- (merged to 'next' on 2022-08-08 at f5a3f88983)
264
- + hook API: don't segfault on strbuf_addf() to NULL "out"
265
-
266
- A follow-up fix to a fix for a regression in 2.36.
267
-
268
- Will merge to 'master' and then to 'maint'.
269
- source: <patch-1.1-2450e3e65cf-20220805T141402Z-avarab@gmail.com>
270
-
271
-
272
-* ab/tech-docs-to-help (2022-08-04) 12 commits
273
- (merged to 'next' on 2022-08-08 at 65c9ec7308)
274
- + docs: move http-protocol docs to man section 5
275
- + docs: move cruft pack docs to gitformat-pack
276
- + docs: move pack format docs to man section 5
277
- + docs: move signature docs to man section 5
278
- + docs: move index format docs to man section 5
279
- + docs: move protocol-related docs to man section 5
280
- + docs: move commit-graph format docs to man section 5
281
- + git docs: add a category for file formats, protocols and interfaces
282
- + git docs: add a category for user-facing file, repo and command UX
283
- + git help doc: use "<doc>" instead of "<guide>"
284
- + help.c: remove common category behavior from drop_prefix() behavior
285
- + help.c: refactor drop_prefix() to use a "switch" statement"
286
-
287
- Expose a lot of "tech docs" via "git help" interface.
288
-
371
Will merge to 'master'.
290
- source: <cover-v8-00.12-00000000000-20220804T162138Z-avarab@gmail.com>
372
+ source: <pull.1312.v3.git.1659985672.gitgitgadget@gmail.com>
373
374
375
* sg/parse-options-subcommand (2022-07-25) 20 commits
@@ -315,9 +397,8 @@ Release tarballs are available at:
397
Introduce the "subcommand" mode to parse-options API and update the
398
command line parser of Git commands with subcommands.
399
318
- Will merge to 'next'?
319
- There are some nits on how the changes are explained, but nothing major.
320
- cf. <xmqqa68x5c1i.fsf@gitster.g>
400
+ Expecting a reroll.
401
+ cf. <20220812152837.GC3790@szeder.dev>
402
source: <20220725123857.2773963-1-szeder.dev@gmail.com>
403
404
@@ -419,7 +500,8 @@ Release tarballs are available at:
500
source: <cover-v2-0.9-00000000000-20220729T081959Z-avarab@gmail.com>
501
502
422
-* cw/remote-object-info (2022-07-28) 6 commits
503
+* cw/remote-object-info (2022-08-13) 7 commits
504
+ - SQUASH???
505
- cat-file: add remote-object-info to batch-command
506
- transport: add client support for object-info
507
- serve: advertise object-info feature
@@ -435,31 +517,7 @@ Release tarballs are available at:
517
source: <20220728230210.2952731-1-calvinwan@google.com>
518
519
438
-* ab/leak-check (2022-07-27) 15 commits
439
- (merged to 'next' on 2022-08-05 at 2a6b9c8432)
440
- + CI: use "GIT_TEST_SANITIZE_LEAK_LOG=true" in linux-leaks
441
- + upload-pack: fix a memory leak in create_pack_file()
442
- + leak tests: mark passing SANITIZE=leak tests as leak-free
443
- + leak tests: don't skip some tests under SANITIZE=leak
444
- + test-lib: have the "check" mode for SANITIZE=leak consider leak logs
445
- + test-lib: add a GIT_TEST_PASSING_SANITIZE_LEAK=check mode
446
- + test-lib: simplify by removing test_external
447
- + tests: move copy/pasted PERL + Test::More checks to a lib-perl.sh
448
- + t/Makefile: don't remove test-results in "clean-except-prove-cache"
449
- + test-lib: add a SANITIZE=leak logging mode
450
- + t/README: reword the "GIT_TEST_PASSING_SANITIZE_LEAK" description
451
- + test-lib: add a --invert-exit-code switch
452
- + test-lib: fix GIT_EXIT_OK logic errors, use BAIL_OUT
453
- + test-lib: don't set GIT_EXIT_OK before calling test_atexit_handler
454
- + test-lib: use $1, not $@ in test_known_broken_{ok,failure}_
455
-
456
- Extend SANITIZE=leak checking and declare more tests "currently leak-free".
457
-
458
- Will merge to 'master'.
459
- source: <cover-v3-00.15-00000000000-20220727T230800Z-avarab@gmail.com>
460
-
461
-
462
-* mt/rot13-in-c (2022-07-31) 4 commits
520
+* mt/rot13-in-c (2022-08-14) 4 commits
521
- tests: use the new C rot13-filter helper to avoid PERL prereq
522
- t0021: implementation the rot13-filter.pl script in C
523
- t0021: avoid grepping for a Perl-specific string at filter output
@@ -467,20 +525,16 @@ Release tarballs are available at:
525
526
Test portability improvements.
527
470
- Expecting a reroll.
471
- cf. <CAHd-oW6GLf=4VxAvMy6c9jrGx1zcSHbe_NKbAUg7wvNBPOmEXw@mail.gmail.com>
472
- source: <cover.1659291025.git.matheus.bernardino@usp.br>
528
+ Will merge to 'next'?
529
+ source: <cover.1660522524.git.matheus.bernardino@usp.br>
530
531
475
-* tl/trace2-config-scope (2022-07-22) 2 commits
532
+* tl/trace2-config-scope (2022-08-11) 2 commits
533
- tr2: shows scope unconditionally in addition to key-value pair
534
- api-trace2.txt: print config key-value pair
535
536
Tweak trace2 output about configuration variables.
480
-
481
- Needs reviewer response
482
- cf. <20220801122515.23146-1-tenglong.tl@alibaba-inc.com>
483
- source: <cover.1658472474.git.dyroneteng@gmail.com>
537
+ source: <cover.1660272404.git.dyroneteng@gmail.com>
538
539
540
* ab/submodule-helper-leakfix (2022-08-03) 18 commits
@@ -511,29 +565,14 @@ Release tarballs are available at:
565
566
567
* cw/submodule-merge-messages (2022-08-04) 1 commit
514
- - submodule merge: update conflict error message
568
+ (merged to 'next' on 2022-08-12 at ede0890319)
569
+ + submodule merge: update conflict error message
570
571
Update the message given when "git merge" sees conflicts at a path
572
with a submodule while merging a superproject.
573
519
- Will merge to 'next'?
520
- source: <20220804195105.1303455-1-calvinwan@google.com>
521
-
522
-
523
-* js/safe-directory-plus (2022-08-08) 5 commits
524
- (merged to 'next' on 2022-08-10 at 3d32a87210)
525
- + mingw: handle a file owned by the Administrators group correctly
526
- + mingw: be more informative when ownership check fails on FAT32
527
- + mingw: provide details about unsafe directories' ownership
528
- + setup: prepare for more detailed "dubious ownership" messages
529
- + setup: fix some formatting
530
-
531
- Platform-specific code that determines if a directory is OK to use
532
- as a repository has been taught to report more details, especially
533
- on Windows.
534
-
574
Will merge to 'master'.
536
- source: <pull.1286.v2.git.1659965270.gitgitgadget@gmail.com>
575
+ source: <20220804195105.1303455-1-calvinwan@google.com>
576
577
578
* po/doc-add-renormalize (2022-08-10) 1 commit
@@ -559,21 +598,18 @@ Release tarballs are available at:
598
source: <pull.1282.git.1657385781.gitgitgadget@gmail.com>
599
600
562
-* ac/bitmap-lookup-table (2022-07-20) 6 commits
601
+* ac/bitmap-lookup-table (2022-08-14) 6 commits
602
- bitmap-lookup-table: add performance tests for lookup table
564
- - p5310-pack-bitmaps.sh: enable `pack.writeReverseIndex`
603
- pack-bitmap: prepare to read lookup table extension
604
- pack-bitmap-write: learn pack.writeBitmapLookupTable and add tests
605
- pack-bitmap-write.c: write lookup table extension
606
+ - bitmap: move `get commit positions` code to `bitmap_writer_finish`
607
- Documentation/technical: describe bitmap lookup table extension
608
609
The pack bitmap file gained a bitmap-lookup table to speed up
610
locating the necessary bitmap for a given commit.
611
573
- Expecting a reroll.
574
- Seems to be flaky-broken under SHA-256.
575
- cf. <p3r70610-8n52-s8q0-n641-onp4ps01330n@tzk.qr>
576
- source: <pull.1266.v5.git.1658342304.gitgitgadget@gmail.com>
612
+ source: <pull.1266.v6.git.1660496112.gitgitgadget@gmail.com>
613
614
615
* jt/connected-show-missing-from-which-side (2022-06-10) 1 commit
@@ -602,12 +638,13 @@ Release tarballs are available at:
638
639
640
* ds/bundle-uri-more (2022-08-10) 2 commits
605
- - bundle-uri: add example bundle organization
606
- - docs: document bundle URI standard
641
+ (merged to 'next' on 2022-08-12 at 4f445a058d)
642
+ + bundle-uri: add example bundle organization
643
+ + docs: document bundle URI standard
644
645
The "bundle URI" design gets documented.
646
610
- Will merge to 'next'.
647
+ Will merge to 'master'.
648
source: <pull.1248.v4.git.1660050761.gitgitgadget@gmail.com>
649
650