What's cooking (2024/05 #01)
Junio C Hamano committed
May 1, 2024 at 12:01 UTC
a95c444b0d35f83cb4ba9ac1b3305a565d1e8701
1 file changed
+204
-169
whats-cooking.txt
+204
-169
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Apr 2024, #10; Mon, 29)
3
-X-master-at: 786a3e4b8d754d2b14b1208b98eeb0a554ef19a8
4
-X-next-at: b9fe23f5ca751025eab840f4e693bd4f1ac413cb
2
+Subject: What's cooking in git.git (May 2024, #01; Wed, 1)
3
+X-master-at: d4cc1ec35f3bcce816b69986ca41943f6ce21377
4
+X-next-at: 0667e3c05b4d9d32988313da24324a4cf9ecb0bf
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Apr 2024, #10; Mon, 29)
7
+What's cooking in git.git (May 2024, #01; Wed, 1)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -17,7 +17,8 @@ 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
-Git 2.45 has been tagged.
20
+The first batch of topics for the new cycle have graduated to the
21
+'master' branch, and the tip of 'next' has been rewound.
22
23
Copies of the source code to Git live in many repositories, and the
24
following is a list of the ones I push into or their mirrors. Some
@@ -50,28 +51,165 @@ Release tarballs are available at:
51
--------------------------------------------------
52
[Graduated to 'master']
53
53
-* rj/add-i-leak-fix (2024-04-22) 4 commits
54
- (merged to 'next' on 2024-04-23 at b10e350a54)
55
- + add: plug a leak on interactive_add
56
- + add-patch: plug a leak handling the '/' command
57
- + add-interactive: plug a leak in get_untracked_files
58
- + apply: plug a leak in apply_data
54
+* aj/stash-staged-fix (2024-04-22) 1 commit
55
+ (merged to 'next' on 2024-04-23 at d49e9dade0)
56
+ + stash: fix "--staged" with binary files
57
+
58
+ "git stash -S" did not handle binary files correctly, which has
59
+ been corrected.
60
+ source: <pull.1722.git.1713781694490.gitgitgadget@gmail.com>
61
+
62
+
63
+* ds/format-patch-rfc-and-k (2024-04-19) 1 commit
64
+ (merged to 'next' on 2024-04-23 at b3b0c5507a)
65
+ + format-patch: ensure that --rfc and -k are mutually exclusive
66
+
67
+ The "-k" and "--rfc" options of "format-patch" will now error out
68
+ when used together, as one tells us not to add anything to the
69
+ title of the commit, and the other one tells us to add "RFC" in
70
+ addition to "PATCH".
71
+ source: <71d195c248879e7c46fac0e84c6b0a8aa90bd2c2.1713488563.git.dsimic@manjaro.org>
72
+
73
+
74
+* jc/format-patch-rfc-more (2024-04-23) 2 commits
75
+ (merged to 'next' on 2024-04-23 at 9f51487974)
76
+ + format-patch: "--rfc=-(WIP)" appends to produce [PATCH (WIP)]
77
+ + format-patch: allow --rfc to optionally take a value, like --rfc=WIP
78
+
79
+ The "--rfc" option of "git format-patch" learned to take an
80
+ optional string value to be used in place of "RFC" to tweak the
81
+ "[PATCH]" on the subject header.
82
+ source: <20240423175234.170434-1-gitster@pobox.com>
83
+
84
60
- Leakfix.
61
- source: <69f86760-96ff-4c62-9649-4627652b7c19@gmail.com>
85
+* js/build-fuzz-more-often (2024-04-24) 1 commit
86
+ (merged to 'next' on 2024-04-25 at 28f65d1be2)
87
+ + fuzz: link fuzz programs with `make all` on Linux
88
+
89
+ In addition to building the objects needed, try to link the objects
90
+ that are used in fuzzer tests, to make sure at least they build
91
+ without bitrot, in Linux CI runs.
92
+ source: <ba9d24c6445de309226bf7c165499f1969807fef.1713982389.git.steadmon@google.com>
93
94
64
-* rs/vsnprintf-failure-is-not-a-bug (2024-04-21) 1 commit
65
- (merged to 'next' on 2024-04-23 at bf66ab6ea7)
66
- + don't report vsnprintf(3) error as bug
95
+* js/for-each-repo-keep-going (2024-04-24) 2 commits
96
+ (merged to 'next' on 2024-04-25 at d33253d919)
97
+ + maintenance: running maintenance should not stop on errors
98
+ + for-each-repo: optionally keep going on an error
99
+
100
+ A scheduled "git maintenance" job is expected to work on all
101
+ repositories it knows about, but it stopped at the first one that
102
+ errored out. Now it keeps going.
103
+ source: <pull.1719.v3.git.1713975299.gitgitgadget@gmail.com>
104
+
105
68
- Demote a BUG() to an die() when the failure from vsnprintf() may
69
- not be due to a programmer error.
70
- source: <ea752a2b-9b74-4a59-a037-4782abf7161e@web.de>
106
+* la/doc-use-of-contacts-when-contributing (2024-04-18) 8 commits
107
+ (merged to 'next' on 2024-04-25 at 5102a45f63)
108
+ + SubmittingPatches: demonstrate using git-contacts with git-send-email
109
+ + SubmittingPatches: add heading for format-patch and send-email
110
+ + SubmittingPatches: dedupe discussion of security patches
111
+ + SubmittingPatches: discuss reviewers first
112
+ + SubmittingPatches: quote commands
113
+ + SubmittingPatches: mention GitGitGadget
114
+ + SubmittingPatches: clarify 'git-contacts' location
115
+ + MyFirstContribution: mention contrib/contacts/git-contacts
116
+
117
+ Advertise "git contacts", a tool for newcomers to find people to
118
+ ask review for their patches, a bit more in our developer
119
+ documentation.
120
+ source: <pull.1704.v6.git.1713477125.gitgitgadget@gmail.com>
121
+
122
+
123
+* pw/rebase-m-signoff-fix (2024-04-18) 6 commits
124
+ (merged to 'next' on 2024-04-23 at 66374c00e2)
125
+ + rebase -m: fix --signoff with conflicts
126
+ + sequencer: store commit message in private context
127
+ + sequencer: move current fixups to private context
128
+ + sequencer: start removing private fields from public API
129
+ + sequencer: always free "struct replay_opts"
130
+ + Merge branch 'pw/t3428-cleanup' into pw/rebase-m-signoff-fix
131
+
132
+ "git rebase --signoff" used to forget that it needs to add a
133
+ sign-off to the resulting commit when told to continue after a
134
+ conflict stops its operation.
135
+ source: <cover.1713445918.git.phillip.wood@dunelm.org.uk>
136
+
137
+
138
+* xx/disable-replace-when-building-midx (2024-04-17) 1 commit
139
+ (merged to 'next' on 2024-04-23 at 6c8f41740e)
140
+ + midx: disable replace objects
141
+
142
+ The procedure to build multi-pack-index got confused by the
143
+ replace-refs mechanism, which has been corrected by disabling the
144
+ latter.
145
+ source: <pull.1711.v2.git.1712554017808.gitgitgadget@gmail.com>
146
147
--------------------------------------------------
148
[New Topics]
149
150
+* bb/rgb-12-bit-colors (2024-04-30) 4 commits
151
+ - fixup! t/t4026-color: add test coverage for invalid RGB colors
152
+ - color: add support for 12-bit RGB colors
153
+ - t/t4026-color: add test coverage for invalid RGB colors
154
+ - t/t4026-color: remove an extra double quote character
155
+
156
+ Colors can now be specified with 12-bit format "#RGB" (in addition
157
+ to "#RRGGBB" that is already supported).
158
+
159
+ Will merge to 'next' after squashing the fix-up in???
160
+ source: <20240429164849.78509-1-dev+git@drbeat.li>
161
+
162
+
163
+* ds/scalar-reconfigure-all-fix (2024-04-30) 1 commit
164
+ - scalar: avoid segfault in reconfigure --all
165
+
166
+ Scalar fix.
167
+
168
+ Comments?
169
+ source: <pull.1724.git.1714496333004.gitgitgadget@gmail.com>
170
+
171
+
172
+* ps/pseudo-ref-terminology (2024-04-30) 10 commits
173
+ - refs: refuse to write pseudorefs
174
+ - ref-filter: properly distinuish pseudo and root refs
175
+ - refs: pseudorefs are no refs
176
+ - refs: root refs can be symbolic refs
177
+ - refs: classify HEAD as a root ref
178
+ - refs: refname `is_special_ref()` to `is_pseudo_ref()`
179
+ - refs: rename `is_pseudoref()` to `is_root_ref()`
180
+ - Documentation/glossary: define root refs as refs
181
+ - Documentation/glossary: clarify limitations of pseudorefs
182
+ - Documentation/glossary: redefine pseudorefs as special refs
183
+
184
+ Terminology to call various ref-like things are getting
185
+ straightened out.
186
+
187
+ Under discussion.
188
+ source: <cover.1714479928.git.ps@pks.im>
189
+
190
+
191
+* dk/zsh-git-repo-path-fix (2024-04-30) 1 commit
192
+ - completion: zsh: stop leaking local cache variable
193
+
194
+ Command line completion support for zsh (in contrib/) has been
195
+ updated to stop exposing internal state to end-user shell
196
+ interaction.
197
+
198
+ Will merge to 'next'.
199
+ source: <pull.1725.git.1714513995564.gitgitgadget@gmail.com>
200
+
201
+
202
+* rs/diff-parseopts-cleanup (2024-05-01) 1 commit
203
+ - diff-lib: stop calling diff_setup_done() in do_diff_cache()
204
+
205
+ Code clean-up to remove code that is now a noop.
206
+
207
+ Will merge to 'next'.
208
+ source: <0e96c5a3-7b4d-4c6b-875e-d80e3eb07a00@web.de>
209
+
210
+--------------------------------------------------
211
+[Cooking]
212
+
213
* rh/complete-symbolic-ref (2024-04-25) 3 commits
214
- completion: add docs on how to add subcommand completions
215
- completion: improve docs for using __git_complete
@@ -98,18 +236,26 @@ Release tarballs are available at:
236
- vimdiff: make script and tests work with zsh
237
- t4046: avoid continue in &&-chain for zsh
238
239
+ zsh can pretend to be a normal shell pretty well except for some
240
+ glitches that we tickle in some of our scripts. Work them around
241
+ so that "vimdiff" and our test suite works well enough with it.
242
+
243
+ Will merge to 'next'.
244
source: <20240426221154.2194139-1-sandals@crustytoothpaste.net>
245
246
104
-* jc/rev-parse-fatal-doc (2024-04-28) 1 commit
105
- - rev-parse: document that most of the time you need to be in a repository
247
+* jc/rev-parse-fatal-doc (2024-05-01) 1 commit
248
+ - rev-parse: document how --is-* options work outside a repository
249
107
---------------------------------------------------
108
-[Cooking]
250
+ Doc update.
251
+
252
+ Comments?
253
+ source: <xmqqplu54fbg.fsf@gitster.g>
254
110
-* ps/undecided-is-not-necessarily-sha1 (2024-04-29) 13 commits
111
- - SQUASH???
255
+
256
+* ps/undecided-is-not-necessarily-sha1 (2024-04-30) 13 commits
257
- repository: stop setting SHA1 as the default object hash
258
+ - oss-fuzz/commit-graph: set up hash algorithm
259
- builtin/shortlog: don't set up revisions without repo
260
- builtin/diff: explicitly set hash algo when there is no repo
261
- builtin/bundle: abort "verify" early when there is no repository
@@ -127,59 +273,21 @@ Release tarballs are available at:
273
this will smoke out codepaths that rely on such an unwarranted
274
assumptions.
275
130
- fuzz-smoke-test job at GitHub Actions CI breaks with this in 'seen'
131
- cf. <xmqqwmoi31aw.fsf@gitster.g>
132
- source: <cover.1713848619.git.ps@pks.im>
133
-
134
-
135
-* aj/stash-staged-fix (2024-04-22) 1 commit
136
- (merged to 'next' on 2024-04-23 at d49e9dade0)
137
- + stash: fix "--staged" with binary files
138
-
139
- "git stash -S" did not handle binary files correctly, which has
140
- been corrected.
141
-
142
- Will cook in 'next'.
143
- source: <pull.1722.git.1713781694490.gitgitgadget@gmail.com>
276
+ Comments?
277
+ source: <cover.1714371422.git.ps@pks.im>
278
279
146
-* rj/add-p-typo-reaction (2024-04-26) 1 commit
280
+* rj/add-p-typo-reaction (2024-04-30) 2 commits
281
- add-patch: response to unknown command
282
+ - add-patch: do not show UI messages on stderr
283
284
When the user responds to a prompt given by "git add -p" with an
285
unsupported command, list of available commands were given, which
286
was too much if the user knew what they wanted to type but merely
287
made a typo. Now the user gets a much shorter error message.
288
154
- Expecting a reroll.
155
- cf. <305296f1-975b-41b9-968c-3984d8056196@gmail.com>
156
- source: <b209a2b8-f98f-4f14-a687-9022d30968dd@gmail.com>
157
-
158
-
159
-* ds/format-patch-rfc-and-k (2024-04-19) 1 commit
160
- (merged to 'next' on 2024-04-23 at b3b0c5507a)
161
- + format-patch: ensure that --rfc and -k are mutually exclusive
162
-
163
- The "-k" and "--rfc" options of "format-patch" will now error out
164
- when used together, as one tells us not to add anything to the
165
- title of the commit, and the other one tells us to add "RFC" in
166
- addition to "PATCH".
167
-
168
- Will cook in 'next'.
169
- source: <71d195c248879e7c46fac0e84c6b0a8aa90bd2c2.1713488563.git.dsimic@manjaro.org>
170
-
171
-
172
-* jc/format-patch-rfc-more (2024-04-23) 2 commits
173
- (merged to 'next' on 2024-04-23 at 9f51487974)
174
- + format-patch: "--rfc=-(WIP)" appends to produce [PATCH (WIP)]
175
- + format-patch: allow --rfc to optionally take a value, like --rfc=WIP
176
-
177
- The "--rfc" option of "git format-patch" learned to take an
178
- optional string value to be used in place of "RFC" to tweak the
179
- "[PATCH]" on the subject header.
180
-
181
- Will cook in 'next'.
182
- source: <20240423175234.170434-1-gitster@pobox.com>
289
+ Will merge to 'next'.
290
+ source: <952a9514-3cf1-4601-8f0d-db57adc750c3@gmail.com>
291
292
293
* ps/the-index-is-no-more (2024-04-18) 6 commits
@@ -194,52 +302,10 @@ Release tarballs are available at:
302
by always instantiating "the_repository" and replacing references
303
to "the_index" with references to its .index member.
304
197
- Will merge to 'next'?
305
+ Will merge to 'next'.
306
source: <cover.1713442061.git.ps@pks.im>
307
308
201
-* pw/rebase-m-signoff-fix (2024-04-18) 6 commits
202
- (merged to 'next' on 2024-04-23 at 66374c00e2)
203
- + rebase -m: fix --signoff with conflicts
204
- + sequencer: store commit message in private context
205
- + sequencer: move current fixups to private context
206
- + sequencer: start removing private fields from public API
207
- + sequencer: always free "struct replay_opts"
208
- + Merge branch 'pw/t3428-cleanup' into pw/rebase-m-signoff-fix
209
-
210
- "git rebase --signoff" used to forget that it needs to add a
211
- sign-off to the resulting commit when told to continue after a
212
- conflict stops its operation.
213
-
214
- Will cook in 'next'.
215
- source: <cover.1713445918.git.phillip.wood@dunelm.org.uk>
216
-
217
-
218
-* js/for-each-repo-keep-going (2024-04-24) 2 commits
219
- (merged to 'next' on 2024-04-25 at d33253d919)
220
- + maintenance: running maintenance should not stop on errors
221
- + for-each-repo: optionally keep going on an error
222
-
223
- A scheduled "git maintenance" job is expected to work on all
224
- repositories it knows about, but it stopped at the first one that
225
- errored out. Now it keeps going.
226
-
227
- Will cook in 'next'.
228
- source: <pull.1719.v3.git.1713975299.gitgitgadget@gmail.com>
229
-
230
-
231
-* xx/disable-replace-when-building-midx (2024-04-17) 1 commit
232
- (merged to 'next' on 2024-04-23 at 6c8f41740e)
233
- + midx: disable replace objects
234
-
235
- The procedure to build multi-pack-index got confused by the
236
- replace-refs mechanism, which has been corrected by disabling the
237
- latter.
238
-
239
- Will cook in 'next'.
240
- source: <pull.1711.v2.git.1712554017808.gitgitgadget@gmail.com>
241
-
242
-
309
* kn/update-ref-symrefs (2024-04-26) 7 commits
310
- ref: support symrefs in 'reference-transaction' hook
311
- update-ref: add support for 'symref-update' command
@@ -256,25 +322,6 @@ Release tarballs are available at:
322
source: <20240426152449.228860-1-knayak@gitlab.com>
323
324
259
-* la/doc-use-of-contacts-when-contributing (2024-04-18) 8 commits
260
- (merged to 'next' on 2024-04-25 at 5102a45f63)
261
- + SubmittingPatches: demonstrate using git-contacts with git-send-email
262
- + SubmittingPatches: add heading for format-patch and send-email
263
- + SubmittingPatches: dedupe discussion of security patches
264
- + SubmittingPatches: discuss reviewers first
265
- + SubmittingPatches: quote commands
266
- + SubmittingPatches: mention GitGitGadget
267
- + SubmittingPatches: clarify 'git-contacts' location
268
- + MyFirstContribution: mention contrib/contacts/git-contacts
269
-
270
- Advertise "git contacts", a tool for newcomers to find people to
271
- ask review for their patches, a bit more in our developer
272
- documentation.
273
-
274
- Will cook in 'next'.
275
- source: <pull.1704.v6.git.1713477125.gitgitgadget@gmail.com>
276
-
277
-
325
* ps/ci-test-with-jgit (2024-04-12) 13 commits
326
- t0612: add tests to exercise Git/JGit reftable compatibility
327
- t0610: fix non-portable variable assignment
@@ -311,22 +358,23 @@ Release tarballs are available at:
358
359
360
* ps/reftable-write-optim (2024-04-08) 11 commits
314
- - reftable/block: reuse compressed array
315
- - reftable/block: reuse zstream when writing log blocks
316
- - reftable/writer: reset `last_key` instead of releasing it
317
- - reftable/writer: unify releasing memory
318
- - reftable/writer: refactorings for `writer_flush_nonempty_block()`
319
- - reftable/writer: refactorings for `writer_add_record()`
320
- - refs/reftable: don't recompute committer ident
321
- - reftable: remove name checks
322
- - refs/reftable: skip duplicate name checks
323
- - refs/reftable: perform explicit D/F check when writing symrefs
324
- - refs/reftable: fix D/F conflict error message on ref copy
361
+ (merged to 'next' on 2024-04-30 at 0667e3c05b)
362
+ + reftable/block: reuse compressed array
363
+ + reftable/block: reuse zstream when writing log blocks
364
+ + reftable/writer: reset `last_key` instead of releasing it
365
+ + reftable/writer: unify releasing memory
366
+ + reftable/writer: refactorings for `writer_flush_nonempty_block()`
367
+ + reftable/writer: refactorings for `writer_add_record()`
368
+ + refs/reftable: don't recompute committer ident
369
+ + reftable: remove name checks
370
+ + refs/reftable: skip duplicate name checks
371
+ + refs/reftable: perform explicit D/F check when writing symrefs
372
+ + refs/reftable: fix D/F conflict error message on ref copy
373
374
Code to write out reftable has seen some optimization and
375
simplification.
376
329
- Will merge to 'next'?
377
+ Will merge to 'master'.
378
source: <cover.1712578837.git.ps@pks.im>
379
380
@@ -337,7 +385,7 @@ Release tarballs are available at:
385
"git send-email" learned to separate its reports on each message it
386
sends out with an extra blank line in between.
387
340
- Will merge to 'next'?
388
+ Comments?
389
source: <cover.1712732383.git.dsimic@manjaro.org>
390
391
@@ -376,11 +424,11 @@ Release tarballs are available at:
424
been enhanced to support authentication schemes different from
425
username & password pair, like Bearer and NTLM.
426
379
- Comments?
427
+ Will merge to 'next'.
428
source: <20240417000240.3611948-1-sandals@crustytoothpaste.net>
429
430
383
-* tb/pseudo-merge-reachability-bitmap (2024-03-20) 24 commits
431
+* tb/pseudo-merge-reachability-bitmap (2024-04-30) 23 commits
432
- t/perf: implement performace tests for pseudo-merge bitmaps
433
- pseudo-merge: implement support for finding existing merges
434
- ewah: `bitmap_equals_ewah()`
@@ -403,7 +451,6 @@ Release tarballs are available at:
451
- pack-bitmap: move some initialization to `bitmap_writer_init()`
452
- pack-bitmap: drop unused `max_bitmaps` parameter
453
- ewah: implement `ewah_bitmap_is_subset()`
406
- - config: repo_config_get_expiry()
454
- Documentation/technical: describe pseudo-merge bitmaps format
455
456
The pack-bitmap machinery learned to write pseudo-merge bitmaps,
@@ -411,9 +458,8 @@ Release tarballs are available at:
458
reference tips. This enhances bitmap coverage, and thus,
459
performance, for repositories with many references using bitmaps.
460
414
- Expecting a reroll.
415
- cf. <ZfyxCLpjbaScIdWA@nand.local>
416
- source: <cover.1710972293.git.me@ttaylorr.com>
461
+ Needs review.
462
+ source: <cover.1714422410.git.me@ttaylorr.com>
463
464
465
* la/hide-trailer-info (2024-04-26) 11 commits
@@ -427,12 +473,12 @@ Release tarballs are available at:
473
- trailer: teach iterator about non-trailer lines
474
- trailer: add unit tests for trailer iterator
475
- Makefile: sort UNIT_TEST_PROGRAMS
430
- + Merge branch 'la/format-trailer-info' into la/hide-trailer-info
476
+ - Merge branch 'la/format-trailer-info' into la/hide-trailer-info
477
478
The trailer API has been reshuffled a bit.
479
434
- Will merge to 'next'?
435
- cf. <CAP8UFD0ZHpo7US6dx_WK6F_1JYsBdHunBaW86qM1CzOKaPC-aA@mail.gmail.com>
480
+ Expecting a hopefully final reroll.
481
+ cf. <CAMo6p=GRcmy6NDGRskuNrauMYTkAgk_p_0TJJTPC2=axVrWuvQ@mail.gmail.com>
482
source: <pull.1696.v3.git.1714091170.gitgitgadget@gmail.com>
483
484
@@ -459,18 +505,6 @@ Release tarballs are available at:
505
source: <20240319183722.211300-1-ignacio@iencinas.com>
506
507
462
-* js/build-fuzz-more-often (2024-04-24) 1 commit
463
- (merged to 'next' on 2024-04-25 at 28f65d1be2)
464
- + fuzz: link fuzz programs with `make all` on Linux
465
-
466
- In addition to building the objects needed, try to link the objects
467
- that are used in fuzzer tests, to make sure at least they build
468
- without bitrot, in Linux CI runs.
469
-
470
- Will cook in 'next'.
471
- source: <ba9d24c6445de309226bf7c165499f1969807fef.1713982389.git.steadmon@google.com>
472
-
473
-
508
* cw/git-std-lib (2024-02-28) 4 commits
509
- SQUASH??? get rid of apparent debugging crufts
510
- test-stdlib: show that git-std-lib is independent
@@ -483,7 +517,7 @@ Release tarballs are available at:
517
source: <cover.1696021277.git.jonathantanmy@google.com>
518
519
486
-* js/cmake-with-test-tool (2024-04-24) 2 commits
520
+* js/cmake-with-test-tool (2024-04-30) 2 commits
521
- cmake: let `test-tool` run the unit tests, too
522
- Merge branch 'js/unit-test-suite-runner' into js/cmake-with-test-tool
523
(this branch uses js/unit-test-suite-runner.)
@@ -491,11 +525,12 @@ Release tarballs are available at:
525
"test-tool" is now built in CMake build to also run the unit tests.
526
527
May want to roll it into the base topic.
528
+
529
Will merge to 'next' together with the base topic.
530
source: <pull.1666.git.1708038924522.gitgitgadget@gmail.com>
531
532
498
-* js/unit-test-suite-runner (2024-04-24) 8 commits
533
+* js/unit-test-suite-runner (2024-04-30) 8 commits
534
- ci: use test-tool as unit test runner on Windows
535
- t/Makefile: run unit tests alongside shell tests
536
- unit tests: add rule for running with test-tool
@@ -509,8 +544,8 @@ Release tarballs are available at:
544
The "test-tool" has been taught to run testsuite tests in parallel,
545
bypassing the need to use the "prove" tool.
546
512
- Needs review.
513
- source: <cover.1713985716.git.steadmon@google.com>
547
+ Will merge to 'next'?
548
+ source: <cover.1714506612.git.steadmon@google.com>
549
550
551
* bk/complete-dirname-for-am-and-format-patch (2024-01-12) 1 commit