What's cooking (2022/10 #01)
Junio C Hamano committed
Oct 3, 2022 at 01:23 UTC
342535a0192e9f6f6c49ce8e9179c121e7071854
1 file changed
+93
-81
whats-cooking.txt
+93
-81
@@ -1,9 +1,9 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Sep 2022, #09; Fri, 30)
3
-X-master-at: bcd6bc478adc4951d57ec597c44b12ee74bc88fb
4
-X-next-at: 84df46c1b469daf986023931247b98d22e07f24d
2
+Subject: What's cooking in git.git (Oct 2022, #01; Sun, 2)
3
+X-master-at: 3dcec76d9df911ed8321007b1d197c1a206dc164
4
+X-next-at: 74048e4d9e2b6a27a4fab355a907e0c38d172bfd
5
6
-What's cooking in git.git (Sep 2022, #09; Fri, 30)
6
+What's cooking in git.git (Oct 2022, #01; Sun, 2)
7
--------------------------------------------------
8
9
Here are the topics that have been cooking in my tree. Commits
@@ -13,16 +13,19 @@ 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
-The -rc2 has been tagged for this cycle. People are free to discuss
17
-topics that has no relevance to the upcoming release, but we would
18
-appreciate if they instead concentrated on finding and fixing recent
19
-regressions in the upcoming release. Even though I may be replacing
20
-topics in 'seen' with their new iterations, I may not be picking up
21
-patches on new topics to 'seen', until the final around the
22
-beginning of the next month (cf. https://tinyurl.com/gitCal). These
23
-patches are welcome to come back in a more polished form after that
24
-happens (read: discussions on them are not forbidden. just allow me
25
-to leave my tree less distracted by new topics).
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.
29
30
Copies of the source code to Git live in many repositories, and the
31
following is a list of the ones I push into or their mirrors. Some
@@ -55,57 +58,15 @@ Release tarballs are available at:
58
--------------------------------------------------
59
[New Topics]
60
58
-* jc/branch-description-unset (2022-09-30) 1 commit
59
- - branch: do not fail a no-op --edit-desc
61
+* jc/tmp-objdir (2022-09-30) 1 commit
62
+ - tmp-objdir: skip clean up when handling a signal
63
61
- "GIT_EDITOR=: git branch --edit-description" resulted in failure,
62
- which has been corrected.
63
-
64
- Needs review.
65
- source: <xmqqmtagka8x.fsf@gitster.g>
66
-
67
-
68
-* rj/branch-edit-desc-unborn (2022-09-27) 1 commit
69
- - branch: description for non-existent branch errors
70
-
71
- "git branch --edit-description" on an unborh branch misleadingly
72
- said that no such branch exists, which has been corrected.
73
-
74
- Expecting a reroll to update proposed log message and add tests.
75
- cf. <xmqqleq6ovh4.fsf@gitster.g>
76
- source: <858edf12-67b1-5e2c-dd2e-3eb476530803@gmail.com>
77
-
78
-
79
-* ab/test-malloc-with-sanitize-leak (2022-09-29) 1 commit
80
- (merged to 'next' on 2022-09-29 at b6fef2dd1f)
81
- + test-lib: have SANITIZE=leak imply TEST_NO_MALLOC_CHECK
82
-
83
- Test fix.
84
-
85
- Will cook in 'next'.
86
- source: <patch-1.1-e31681731b7-20220928T095041Z-avarab@gmail.com>
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.
67
88
-
89
-* ah/branch-autosetupmerge-grammofix (2022-09-28) 1 commit
90
- (merged to 'next' on 2022-09-29 at 622b75f0da)
91
- + push: improve grammar of branch.autoSetupMerge advice
92
-
93
- Fix grammar of a message introduced in previous round.
94
-
95
- Will cook in 'next'.
96
- source: <20220928055811.777227-1-alexhenrie24@gmail.com>
97
-
98
-
99
-* jt/promisor-remote-fetch-tweak (2022-09-29) 2 commits
100
- - promisor-remote: die upon failing fetch
101
- - promisor-remote: remove a return value
102
-
103
- Remove error detection from a function that fetches from promisor
104
- remotes, and make it die when such a fetch fails to bring all the
105
- requested objects, to give an early failure to various operations.
106
-
107
- Needs review.
108
- source: <cover.1664316642.git.jonathantanmy@google.com>
68
+ Will merge to 'next'?
69
+ source: <pull.1348.v4.git.git.1664570831583.gitgitgadget@gmail.com>
70
71
--------------------------------------------------
72
[Stalled]
@@ -147,17 +108,18 @@ Release tarballs are available at:
108
109
110
* cw/remote-object-info (2022-08-13) 7 commits
150
- - SQUASH???
151
- - cat-file: add remote-object-info to batch-command
152
- - transport: add client support for object-info
153
- - serve: advertise object-info feature
154
- - protocol-caps: initialization bug fix
155
- - fetch-pack: move fetch initialization
156
- - fetch-pack: refactor packet writing
111
+ . SQUASH???
112
+ . cat-file: add remote-object-info to batch-command
113
+ . transport: add client support for object-info
114
+ . serve: advertise object-info feature
115
+ . protocol-caps: initialization bug fix
116
+ . fetch-pack: move fetch initialization
117
+ . fetch-pack: refactor packet writing
118
119
A client component to talk with the object-info endpoint.
120
121
Expecting a reroll.
122
+ Under SANITIZE=address, t1006-cat-file.sh finds a breakage.
123
cf. <20220728230210.2952731-1-calvinwan@google.com>
124
cf. <CAFySSZDvgwbbHCHfyuaqX3tKsr-GjJ9iihygg6rNNe46Ys7_EA@mail.gmail.com>
125
source: <20220728230210.2952731-1-calvinwan@google.com>
@@ -165,6 +127,58 @@ Release tarballs are available at:
127
--------------------------------------------------
128
[Cooking]
129
130
+* jc/branch-description-unset (2022-09-30) 1 commit
131
+ - branch: do not fail a no-op --edit-desc
132
+
133
+ "GIT_EDITOR=: git branch --edit-description" resulted in failure,
134
+ which has been corrected.
135
+
136
+ Will merge to 'next'?
137
+ source: <xmqqmtagka8x.fsf@gitster.g>
138
+
139
+
140
+* rj/branch-edit-desc-unborn (2022-09-30) 1 commit
141
+ - branch: description for non-existent branch errors
142
+
143
+ "git branch --edit-description" on an unborh branch misleadingly
144
+ said that no such branch exists, which has been corrected.
145
+
146
+ Will merge to 'next'?
147
+ source: <930ff836-a5c4-0e85-517d-39645f00cd31@gmail.com>
148
+
149
+
150
+* ab/test-malloc-with-sanitize-leak (2022-09-29) 1 commit
151
+ (merged to 'next' on 2022-09-29 at b6fef2dd1f)
152
+ + test-lib: have SANITIZE=leak imply TEST_NO_MALLOC_CHECK
153
+
154
+ Test fix.
155
+
156
+ Will cook in 'next'.
157
+ source: <patch-1.1-e31681731b7-20220928T095041Z-avarab@gmail.com>
158
+
159
+
160
+* ah/branch-autosetupmerge-grammofix (2022-09-28) 1 commit
161
+ (merged to 'next' on 2022-09-29 at 622b75f0da)
162
+ + push: improve grammar of branch.autoSetupMerge advice
163
+
164
+ Fix grammar of a message introduced in previous round.
165
+
166
+ Will cook in 'next'.
167
+ source: <20220928055811.777227-1-alexhenrie24@gmail.com>
168
+
169
+
170
+* jt/promisor-remote-fetch-tweak (2022-09-29) 2 commits
171
+ - promisor-remote: die upon failing fetch
172
+ - promisor-remote: remove a return value
173
+
174
+ Remove error detection from a function that fetches from promisor
175
+ remotes, and make it die when such a fetch fails to bring all the
176
+ requested objects, to give an early failure to various operations.
177
+
178
+ Needs review.
179
+ source: <cover.1664316642.git.jonathantanmy@google.com>
180
+
181
+
182
* rj/ref-filter-get-head-description-leakfix (2022-09-26) 1 commit
183
(merged to 'next' on 2022-09-29 at d05d052eb1)
184
+ ref-filter.c: fix a leak in get_head_description
@@ -419,22 +433,19 @@ Release tarballs are available at:
433
source: <20220915160659.126441-1-gitster@pobox.com>
434
435
422
-* rs/diff-caret-bang-with-parents (2022-09-15) 6 commits
423
- - revision: add parents after child for ^!
424
- - revision: rename add_parents_only() to add_nth_parent()
425
- - revision: factor out add_parents()
426
- - revision: factor out add_parent()
427
- - revision: factor out get_commit()
436
+* rs/diff-caret-bang-with-parents (2022-10-01) 3 commits
437
+ - diff: support ^! for merges
438
+ - revisions.txt: unspecify order of resolved parts of ^!
439
- revision: use strtol_i() for exclude_parent
440
441
"git diff rev^!" did not show combined diff to go to the rev from
442
its parents.
443
444
Needs review.
434
- source: <ba6eea28-fb3a-b376-2529-351727c02f1a@web.de>
445
+ source: <16c49d20-cafc-4b48-3c6b-e11c74c29abb@web.de>
446
447
437
-* ab/doc-synopsis-and-cmd-usage (2022-09-28) 35 commits
448
+* ab/doc-synopsis-and-cmd-usage (2022-09-30) 36 commits
449
- tests: assert consistent whitespace in -h output
450
- tests: start asserting that *.txt SYNOPSIS matches -h output
451
- doc txt & -h consistency: make "worktree" consistent
@@ -458,17 +469,18 @@ Release tarballs are available at:
469
- doc txt & -h consistency: use "<options>", not "<options>..."
470
- stash doc SYNOPSIS & -h: correct padding around "[]()"
471
- doc txt & -h consistency: correct padding around "[]()"
461
- - doc txt & -h consistency: add missing "]" to bugreport "-h"
472
+ - doc txt & -h consistency: balance unbalanced "[" and "]"
473
- doc txt & -h consistency: add "-z" to cat-file "-h"
474
- doc txt & -h consistency: fix incorrect alternates syntax
475
- doc txt & -h consistency: word-wrap
476
+ - doc SYNOPSIS & -h: word-wrap
477
- built-ins: consistently add "\n" between "usage" and options
478
- doc SYNOPSIS & -h: fix incorrect alternates syntax
479
- doc SYNOPSIS: consistently use ' for commands
480
- doc SYNOPSIS: don't use ' for subcommands
481
- blame: use a more detailed usage_msg_optf() error on bad -L
482
- bundle: define subcommand -h in terms of command -h
471
- - builtin/bundle.c: use \t, not fix indentation 2-SP indentation
483
+ - builtin/bundle.c: indent with tabs
484
- CodingGuidelines: update and clarify command-line conventions
485
486
The short-help text shown by "git cmd -h" and the synopsis text
@@ -476,7 +488,7 @@ Release tarballs are available at:
488
consistent.
489
490
Needs review.
479
- source: <cover-v2-00.35-00000000000-20220928T082458Z-avarab@gmail.com>
491
+ source: <cover-v3-00.36-00000000000-20220930T180414Z-avarab@gmail.com>
492
493
494
* ab/coccicheck-incremental (2022-08-31) 9 commits