@matheusbsbs / matheus-bagliano / commits / 3146a6d862

What's cooking (2022/10 #02)

Junio C Hamano committed Oct 6, 2022 at 15:47 UTC 3146a6d862d4c731142d09b97cbd9ed925d02aa5
1 file changed +174 -59
whats-cooking.txt
+174 -59
@@ -1,9 +1,9 @@
1 To: git@vger.kernel.org
2 -Subject: What's cooking in git.git (Oct 2022, #01; Sun, 2)
2 +Subject: What's cooking in git.git (Oct 2022, #02; Thu, 6)
3 X-master-at: 3dcec76d9df911ed8321007b1d197c1a206dc164
4 X-next-at: 74048e4d9e2b6a27a4fab355a907e0c38d172bfd
5
6 -What's cooking in git.git (Oct 2022, #01; Sun, 2)
6 +What's cooking in git.git (Oct 2022, #02; Thu, 6)
7 --------------------------------------------------
8
9 Here are the topics that have been cooking in my tree. Commits
@@ -13,19 +13,10 @@ 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 -Git 2.38 has been tagged. There are many topics that have been
17 -cooking in 'next' and should be ready to graduate, but let's first
18 -see if any brown paper bag regressions are reported, which may
19 -require a quick maintenance track update, before merging them down.
20 -
21 -The cycle toward 2.39 will start after that for real. With holidays
22 -near the end of November in some parts of the world and of December
23 -in many parts of the world, traditionally cycles in Q4 have been
24 -short ones. The 2.39 cycle is planned to last 9 weeks, and I will
25 -go offline at around week #4 for a few weeks, during which an
26 -interim maintainer will take over the daily operation of the
27 -project, until I come back and receive the baton again. Consider it
28 -a bus-factor preparedness exercise.
16 +It seems that there aren't many regressions we need to fix
17 +immediately in the most recent release, so let's start merging some
18 +topics that have already been cooking in 'next' down to 'master' and
19 +also some topics that were kept in 'seen' down to 'next' soonish.
20
21 Copies of the source code to Git live in many repositories, and the
22 following is a list of the ones I push into or their mirrors. Some
@@ -58,15 +49,130 @@ Release tarballs are available at:
49 --------------------------------------------------
50 [New Topics]
51
61 -* jc/tmp-objdir (2022-09-30) 1 commit
62 - - tmp-objdir: skip clean up when handling a signal
52 +* jk/sequencer-missing-author-name-check (2022-10-03) 1 commit
53 + - sequencer: detect author name errors in read_author_script()
54
64 - The code to clean temporary object directories (used for
65 - quarantine) tried to remove them inside its signal handler, which
66 - was a no-no.
55 + Typofix in code.
56
68 - Will merge to 'next'?
69 - source: <pull.1348.v4.git.git.1664570831583.gitgitgadget@gmail.com>
57 + Will merge to 'next'.
58 + source: <YzqhEcTDwMwa8dQX@coredump.intra.peff.net>
59 +
60 +
61 +* pw/mailinfo-b-fix (2022-10-03) 1 commit
62 + - mailinfo -b: fix an out of bounds access
63 +
64 + Fix a logic in "mailinfo -b" that miscomputed the length of a
65 + substring, which lead to an out-of-bounds access.
66 +
67 + Will merge to 'next'.
68 +
69 +
70 +* pw/ssh-sign-report-errors (2022-10-05) 1 commit
71 + - ssh signing: return an error when signature cannot be read
72 +
73 + The codepath to sign learned to report errors when it fails to read
74 + from "ssh-keygen".
75 +
76 + Will merge to 'next'.
77 + source: <pull.1371.v2.git.1664877694430.gitgitgadget@gmail.com>
78 +
79 +
80 +* ab/run-hook-api-cleanup (2022-10-05) 15 commits
81 + - run-command.c: don't copy "ungroup" to "struct parallel_processes"
82 + - run-command.c: don't copy *_fn to "struct parallel_processes"
83 + - run-command API: move *_tr2() users to "run_processes_parallel()"
84 + - run-command API: have run_process_parallel() take an "opts" struct
85 + - run-command API: make run_process_parallel{,_tr2}() thin wrappers
86 + - run-command API: add nascent "struct run_process_parallel_opts"
87 + - run-command.c: add an initializer for "struct parallel_processes"
88 + - run-command API: don't fall back on online_cpus()
89 + - run-command API: make "jobs" parameter an "unsigned int"
90 + - run-command API: have "run_processes_parallel{,_tr2}()" return void
91 + - run-command tests: use "return", not "exit"
92 + - run-command test helper: use "else if" pattern
93 + - run-command tests: test stdout of run_command_parallel()
94 + - submodule tests: reset "trace.out" between "grep" invocations
95 + - hook tests: fix redirection logic error in 96e7225b310
96 +
97 + Move a global variable added as a hack during regression fixes to
98 + its proper place in the API.
99 +
100 + Needs review.
101 + source: <cover-00.15-00000000000-20220930T111343Z-avarab@gmail.com>
102 +
103 +
104 +* nb/doc-mergetool-typofix (2022-10-05) 1 commit
105 + - mergetool.txt: typofix 'overwriten' -> 'overwritten'
106 +
107 + Typofix.
108 +
109 + Will merge to 'next'.
110 + source: <pull.1350.git.git.1664844924663.gitgitgadget@gmail.com>
111 +
112 +
113 +* rs/bisect-start-leakfix (2022-10-05) 1 commit
114 + - bisect--helper: plug strvec leak in bisect_start()
115 +
116 + Code clean-up that results in plugging a leak.
117 +
118 + Expecting a reroll.
119 + cf. <04d393cc-d8c7-ddf7-b235-12082f81c560@web.de>
120 + source: <5c6a4c30-d454-51b6-ec57-9af036b9c4e0@web.de>
121 +
122 +
123 +* rs/gc-pack-refs-simplify (2022-10-05) 1 commit
124 + - gc: simplify maintenance_task_pack_refs()
125 +
126 + Code clean-up.
127 +
128 + Will merge to 'next'.
129 + source: <ab33f72e-d552-7bd7-bf04-3c476d32b5b6@web.de>
130 +
131 +
132 +* rs/test-httpd-in-C-locale (2022-10-06) 1 commit
133 + - t/lib-httpd: pass LANG and LC_ALL to Apache
134 +
135 + Force C locale while running tests around httpd to make sure we can
136 + find expected error messages in the log.
137 +
138 + Will merge to 'next'.
139 + source: <a1699375-c660-13ab-42fb-26a8afe4c376@web.de>
140 +
141 +
142 +* ab/unused-annotation (2022-10-05) 1 commit
143 + - git-compat-util.h: GCC deprecated message arg only in GCC 4.5+
144 +
145 + source: <20221005221928.703750-1-asedeno@google.com>
146 +
147 +
148 +* dd/document-runtime-prefix-better (2022-10-05) 1 commit
149 + - Makefile: clarify runtime relative gitexecdir
150 +
151 + source: <20221006013205.15015-1-congdanhqx@gmail.com>
152 +
153 +
154 +* jk/cleanup-callback-parameters (2022-10-06) 4 commits
155 + - attr: drop DEBUG_ATTR code
156 + - commit: avoid writing to global in option callback
157 + - multi-pack-index: avoid writing to global in option callback
158 + - test-submodule: inline resolve_relative_url() function
159 +
160 + Code clean-up.
161 +
162 + Will merge to 'next'.
163 + source: <Yz7Tjy7Rh8cXVxYQ@coredump.intra.peff.net>
164 + source: <Yz7UhYXvNl6+1GbZ@coredump.intra.peff.net>
165 +
166 +
167 +* pw/test-todo (2022-10-06) 3 commits
168 + - test_todo: allow [verbose] test as the command
169 + - test_todo: allow [!] grep as the command
170 + - tests: add test_todo() to mark known breakages
171 +
172 + RFC for test framework improvement.
173 +
174 + Needs review.
175 + source: <pull.1374.git.1665068476.gitgitgadget@gmail.com>
176
177 --------------------------------------------------
178 [Stalled]
@@ -127,6 +233,17 @@ Release tarballs are available at:
233 --------------------------------------------------
234 [Cooking]
235
236 +* jc/tmp-objdir (2022-09-30) 1 commit
237 + - tmp-objdir: skip clean up when handling a signal
238 +
239 + The code to clean temporary object directories (used for
240 + quarantine) tried to remove them inside its signal handler, which
241 + was a no-no.
242 +
243 + Will merge to 'next'?
244 + source: <pull.1348.v4.git.git.1664570831583.gitgitgadget@gmail.com>
245 +
246 +
247 * jc/branch-description-unset (2022-09-30) 1 commit
248 - branch: do not fail a no-op --edit-desc
249
@@ -153,7 +270,7 @@ Release tarballs are available at:
270
271 Test fix.
272
156 - Will cook in 'next'.
273 + Will merge to 'master'?
274 source: <patch-1.1-e31681731b7-20220928T095041Z-avarab@gmail.com>
275
276
@@ -163,11 +280,11 @@ Release tarballs are available at:
280
281 Fix grammar of a message introduced in previous round.
282
166 - Will cook in 'next'.
283 + Will merge to 'master'?
284 source: <20220928055811.777227-1-alexhenrie24@gmail.com>
285
286
170 -* jt/promisor-remote-fetch-tweak (2022-09-29) 2 commits
287 +* jt/promisor-remote-fetch-tweak (2022-10-05) 2 commits
288 - promisor-remote: die upon failing fetch
289 - promisor-remote: remove a return value
290
@@ -175,8 +292,9 @@ Release tarballs are available at:
292 remotes, and make it die when such a fetch fails to bring all the
293 requested objects, to give an early failure to various operations.
294
178 - Needs review.
179 - source: <cover.1664316642.git.jonathantanmy@google.com>
295 + Will merge to 'next'?
296 + Can somebody give a quick read on the test part of the patch?
297 + source: <cover.1664917853.git.jonathantanmy@google.com>
298
299
300 * rj/ref-filter-get-head-description-leakfix (2022-09-26) 1 commit
@@ -185,7 +303,7 @@ Release tarballs are available at:
303
304 Leakfix.
305
188 - Will cook in 'next'.
306 + Will merge to 'master'?
307 source: <6ff29e96-7f8d-c354-dced-b1b363e54467@gmail.com>
308
309
@@ -199,7 +317,7 @@ Release tarballs are available at:
317 "git maintenance unregister" in a repository that is already been
318 unregistered reported an error.
319
202 - Will cook in 'next'.
320 + Will merge to 'master'?
321 source: <pull.1358.v4.git.1664287021.gitgitgadget@gmail.com>
322
323
@@ -210,7 +328,7 @@ Release tarballs are available at:
328 "git clone" did not like to see the "--bare" and the "--origin"
329 options used together without a good reason.
330
213 - Will cook in 'next'.
331 + Will merge to 'master'?
332 source: <YyvzVdfQVdysvMp2@coredump.intra.peff.net>
333
334
@@ -223,7 +341,7 @@ Release tarballs are available at:
341 "git fsck" failed to release contents of tree objects already used
342 from the memory, which has been fixed.
343
226 - Will cook in 'next'.
344 + Will merge to 'master'?
345 source: <Yyw0PSVe3YTQGgRS@coredump.intra.peff.net>
346
347
@@ -234,7 +352,7 @@ Release tarballs are available at:
352 "git remote rename" failed to rename a remote without fetch
353 refspec, which has been corrected.
354
237 - Will cook in 'next'.
355 + Will merge to 'master'?
356 source: <YyvzqZ5tmI0UdRAW@coredump.intra.peff.net>
357
358
@@ -247,7 +365,7 @@ Release tarballs are available at:
365 merge result tree object, which it failed (which is not wrong) and
366 led to a segfault (which is bad), which has been corrected.
367
250 - Will cook in 'next'.
368 + Will merge to 'master'?
369 source: <pull.1362.v5.git.1664350162.gitgitgadget@gmail.com>
370
371
@@ -261,7 +379,7 @@ Release tarballs are available at:
379 description, but a few died upon seeing them. The latter were
380 taught to ignore them, too
381
264 - Will cook in 'next'.
382 + Will merge to 'master'?
383 source: <pull.1363.git.1663865974.gitgitgadget@gmail.com>
384
385
@@ -273,7 +391,7 @@ Release tarballs are available at:
391
392 Prepare for GNU [ef]grep that throw warning of their uses.
393
276 - Will cook in 'next'.
394 + Will merge to 'master'.
395 source: <pull.1338.git.git.1663805905554.gitgitgadget@gmail.com>
396
397
@@ -284,7 +402,7 @@ Release tarballs are available at:
402 The codepath that reads from the index v4 had unaligned memory
403 accesses, which has been corrected.
404
287 - Will cook in 'next'.
405 + Will merge to 'master'.
406 source: <pull.1366.v2.git.1664385541084.gitgitgadget@gmail.com>
407
408
@@ -298,7 +416,7 @@ Release tarballs are available at:
416
417 Prepare for GNU [ef]grep that throw warning of their uses.
418
301 - Will cook in 'next'.
419 + Will merge to 'master'.
420 source: <cover.1663765176.git.congdanhqx@gmail.com>
421
422
@@ -315,7 +433,7 @@ Release tarballs are available at:
433 "git multi-pack-index repack/expire" used to repack unreachable
434 cruft into a new pack, which have been corrected.
435
318 - Will cook in 'next'.
436 + Will merge to 'master'?
437 cf. <63a1c3d4-eff3-af10-4263-058c88e74594@github.com>
438 source: <cover.1663638929.git.me@ttaylorr.com>
439
@@ -326,7 +444,7 @@ Release tarballs are available at:
444
445 Fix messages incorrectly marked for translation.
446
329 - Will cook in 'next'.
447 + Will merge to 'master'?
448 source: <20220920050709.326359-1-alexhenrie24@gmail.com>
449
450
@@ -338,7 +456,7 @@ Release tarballs are available at:
456
457 Code clean-up.
458
341 - Will cook in 'next'.
459 + Will merge to 'master'?
460 source: <20220914193102.5275-1-sorganov@gmail.com>
461
462
@@ -349,7 +467,7 @@ Release tarballs are available at:
467 "git rebase -i" can mistakenly attempt to apply a fixup to a commit
468 itself, which has been corrected.
469
352 - Will cook in 'next'.
470 + Will merge to 'master'?
471 source: <20220924222904.1784975-1-aclopte@gmail.com>
472
473
@@ -359,7 +477,7 @@ Release tarballs are available at:
477
478 Source file shuffling.
479
362 - Will cook in 'next'.
480 + Will merge to 'master'.
481 source: <pull.1353.v4.git.1663598215154.gitgitgadget@gmail.com>
482
483
@@ -369,11 +487,11 @@ Release tarballs are available at:
487
488 Code and semantics cleaning.
489
372 - Will cook in 'next'.
490 + Will merge to 'master'?
491 source: <pull.1325.v2.git.git.1663605291172.gitgitgadget@gmail.com>
492
493
376 -* ed/fsmonitor-on-networked-macos (2022-09-28) 6 commits
494 +* ed/fsmonitor-on-networked-macos (2022-10-05) 6 commits
495 - fsmonitor: add documentation for allowRemote and socketDir options
496 - fsmonitor: check for compatability before communicating with fsmonitor
497 - fsmonitor: deal with synthetic firmlinks on macOS
@@ -384,8 +502,8 @@ Release tarballs are available at:
502 By default, use of fsmonitor on a repository on networked
503 filesystem is disabled. Add knobs to make it workable on macOS.
504
387 - Will merge to 'next'?
388 - source: <pull.1326.v14.git.1664395931.gitgitgadget@gmail.com>
505 + Will merge to 'next'.
506 + source: <pull.1326.v15.git.1664904751.gitgitgadget@gmail.com>
507
508
509 * rj/branch-edit-description-with-nth-checkout (2022-09-12) 2 commits
@@ -429,7 +547,7 @@ Release tarballs are available at:
547 Documentation on various Boolean GIT_* environment variables have
548 been clarified.
549
432 - Will cook in 'next'.
550 + Will merge to 'master'?
551 source: <20220915160659.126441-1-gitster@pobox.com>
552
553
@@ -445,7 +563,7 @@ Release tarballs are available at:
563 source: <16c49d20-cafc-4b48-3c6b-e11c74c29abb@web.de>
564
565
448 -* ab/doc-synopsis-and-cmd-usage (2022-09-30) 36 commits
566 +* ab/doc-synopsis-and-cmd-usage (2022-10-05) 34 commits
567 - tests: assert consistent whitespace in -h output
568 - tests: start asserting that *.txt SYNOPSIS matches -h output
569 - doc txt & -h consistency: make "worktree" consistent
@@ -465,7 +583,7 @@ Release tarballs are available at:
583 - doc txt & -h consistency: make output order consistent
584 - doc txt & -h consistency: add or fix optional "--" syntax
585 - doc txt & -h consistency: fix mismatching labels
468 - - t/helper/test-proc-receive.c: use "<options>", not "<options>..."
586 + - doc SYNOPSIS & -h: use "-" to separate words in labels, not "_"
587 - doc txt & -h consistency: use "<options>", not "<options>..."
588 - stash doc SYNOPSIS & -h: correct padding around "[]()"
589 - doc txt & -h consistency: correct padding around "[]()"
@@ -473,22 +591,20 @@ Release tarballs are available at:
591 - doc txt & -h consistency: add "-z" to cat-file "-h"
592 - doc txt & -h consistency: fix incorrect alternates syntax
593 - doc txt & -h consistency: word-wrap
476 - - doc SYNOPSIS & -h: word-wrap
594 - built-ins: consistently add "\n" between "usage" and options
478 - - doc SYNOPSIS & -h: fix incorrect alternates syntax
595 - doc SYNOPSIS: consistently use ' for commands
596 - doc SYNOPSIS: don't use ' for subcommands
481 - - blame: use a more detailed usage_msg_optf() error on bad -L
597 - bundle: define subcommand -h in terms of command -h
598 - builtin/bundle.c: indent with tabs
599 - CodingGuidelines: update and clarify command-line conventions
600 + - tests: assert *.txt SYNOPSIS and -h output
601
602 The short-help text shown by "git cmd -h" and the synopsis text
603 shown at the beginning of "git help cmd" have been made more
604 consistent.
605
606 Needs review.
491 - source: <cover-v3-00.36-00000000000-20220930T180414Z-avarab@gmail.com>
607 + source: <cover-v4-00.34-00000000000-20221004T132211Z-avarab@gmail.com>
608
609
610 * ab/coccicheck-incremental (2022-08-31) 9 commits
@@ -543,7 +659,7 @@ Release tarballs are available at:
659 "git grep" learned to expand the sparse-index more lazily and on
660 demand in a sparse checkout.
661
546 - Will cook in 'next'.
662 + Will merge to 'master'?
663 source: <20220923041842.27817-2-shaoxuan.yuan02@gmail.com>
664
665
@@ -554,12 +670,12 @@ Release tarballs are available at:
670 With a bit of header twiddling, use the native regexp library on
671 macOS instead of the compat/ one.
672
557 - Will cook in 'next'.
558 - cf. <xmqqzgf389k9.fsf@gitster.g>
673 + Will merge to 'master'.
674 source: <20220826085815.2771102-1-dds@aueb.gr>
675
676
562 -* ds/bundle-uri-3 (2022-09-09) 10 commits
677 +* ds/bundle-uri-3 (2022-10-05) 10 commits
678 + - bundle-uri: suppress stderr from remote-https
679 - bundle-uri: fetch a list of bundles
680 - bundle-uri: limit recursion depth for bundle lists
681 - bundle-uri: parse bundle list in config format
@@ -568,7 +684,6 @@ Release tarballs are available at:
684 - bundle-uri: create base key-value pair parsing
685 - bundle-uri: create bundle_list struct and helpers
686 - bundle-uri: use plain string in find_temp_filename()
571 - - bundle-uri: short-circuit capability parsing
687 - Merge branch 'ds/bundle-uri-clone' into ds/bundle-uri-3
688
689 Define the logical elements of a "bundle list", data structure to
@@ -576,7 +691,7 @@ Release tarballs are available at:
691 them.
692
693 Needs review.
579 - source: <pull.1333.v2.git.1662734015.gitgitgadget@gmail.com>
694 + source: <pull.1333.v3.git.1664886860.gitgitgadget@gmail.com>
695
696
697 * js/cmake-updates (2022-08-24) 5 commits