What's cooking (2022/09 #08)
Junio C Hamano committed
Sep 27, 2022 at 13:14 UTC
50476ce4b3caf97e1f3aa05cc03db1c66497ed74
1 file changed
+105
-109
whats-cooking.txt
+105
-109
@@ -1,9 +1,9 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Sep 2022, #07; Fri, 23)
3
-X-master-at: 4fd6c5e44459e6444c2cd93383660134c95aabd1
4
-X-next-at: ed0d419d3c1a574b86ddc99554cdd663ffe0f5be
2
+Subject: What's cooking in git.git (Sep 2022, #08; Tue, 27)
3
+X-master-at: bcd6bc478adc4951d57ec597c44b12ee74bc88fb
4
+X-next-at: b617e1fe3a04e74d5031ffb5a8390a362c0582ef
5
6
-What's cooking in git.git (Sep 2022, #07; Fri, 23)
6
+What's cooking in git.git (Sep 2022, #08; Tue, 27)
7
--------------------------------------------------
8
9
Here are the topics that have been cooking in my tree. Commits
@@ -13,7 +13,7 @@ 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 -rc1 has been tagged for this cycle. People are free to discuss
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
@@ -55,77 +55,118 @@ Release tarballs are available at:
55
--------------------------------------------------
56
[Graduated to 'master']
57
58
-* ac/bitmap-lookup-table (2022-09-23) 1 commit
59
- (merged to 'next' on 2022-09-23 at 8374b2bb46)
60
- + pack-bitmap: improve grammar of "xor chain" error message
58
+* ds/bitmap-lookup-remove-tracing (2022-09-26) 1 commit
59
+ (merged to 'next' on 2022-09-26 at a0d94b95e0)
60
+ + pack-bitmap: remove trace2 region from hot path
61
62
- Grammofix.
63
- source: <20220922025158.415969-1-alexhenrie24@gmail.com>
62
+ Perf-fix.
63
+ source: <pull.1365.v2.git.1664198277250.gitgitgadget@gmail.com>
64
65
+--------------------------------------------------
66
+[New Topics]
67
+
68
+* rj/ref-filter-get-head-description-leakfix (2022-09-26) 1 commit
69
+ - ref-filter.c: fix a leak in get_head_description
70
+
71
+ Leakfix.
72
66
-* jk/list-objects-filter-cleanup (2022-09-22) 1 commit
67
- (merged to 'next' on 2022-09-22 at 60e9c427db)
68
- + list-objects-filter: initialize sub-filter structs
73
+ Will merge to 'next'?
74
+ source: <6ff29e96-7f8d-c354-dced-b1b363e54467@gmail.com>
75
+
76
+--------------------------------------------------
77
+[Stalled]
78
+
79
+* es/mark-gc-cruft-as-experimental (2022-08-03) 2 commits
80
+ - config: let feature.experimental imply gc.cruftPacks=true
81
+ - gc: add tests for --cruft and friends
82
+
83
+ Enable gc.cruftpacks by default for those who opt into
84
+ feature.experimental setting.
85
+
86
+ Expecting a reroll.
87
+ cf. <220804.86a68ke9d5.gmgdl@evledraar.gmail.com>
88
+ cf. <6803b725-526e-a1c8-f15c-a9ed4a144d4c@github.com>
89
+ source: <20220803205721.3686361-1-emilyshaffer@google.com>
90
+
91
+
92
+* es/doc-creation-factor-fix (2022-07-28) 2 commits
93
+ - range-diff: clarify --creation-factor=<factor>
94
+ - format-patch: clarify --creation-factor=<factor>
95
+
96
+ Expecting a reroll by somebody more familiar with the logic
97
+ cf. <xmqqo7wfix7p.fsf@gitster.g>
98
+ source: <7229p500-p2r4-on87-6802-8o90s36rr3s4@tzk.qr>
99
70
- Fix uninitialized memory access in a recent fix-up that is already
71
- in -rc1.
72
- source: <YywsZU9UUoC08UcN@coredump.intra.peff.net>
100
101
+* cw/remote-object-info (2022-08-13) 7 commits
102
+ - SQUASH???
103
+ - cat-file: add remote-object-info to batch-command
104
+ - transport: add client support for object-info
105
+ - serve: advertise object-info feature
106
+ - protocol-caps: initialization bug fix
107
+ - fetch-pack: move fetch initialization
108
+ - fetch-pack: refactor packet writing
109
75
-* ma/scalar-to-main-fix (2022-09-23) 1 commit
76
- (merged to 'next' on 2022-09-23 at 5229e60838)
77
- + cmd-list.perl: fix identifying man sections
110
+ A client component to talk with the object-info endpoint.
111
79
- Fix manpage generation.
80
- source: <20220923080733.1995862-1-martin.agren@gmail.com>
112
+ Expecting a reroll.
113
+ cf. <20220728230210.2952731-1-calvinwan@google.com>
114
+ cf. <CAFySSZDvgwbbHCHfyuaqX3tKsr-GjJ9iihygg6rNNe46Ys7_EA@mail.gmail.com>
115
+ source: <20220728230210.2952731-1-calvinwan@google.com>
116
117
--------------------------------------------------
83
-[New Topics]
118
+[Cooking]
119
85
-* ds/scalar-unregister-idempotent (2022-09-22) 2 commits
120
+* ds/scalar-unregister-idempotent (2022-09-27) 4 commits
121
+ - string-list: document iterator behavior on NULL input
122
+ - gc: replace config subprocesses with API calls
123
- scalar: make 'unregister' idempotent
124
- maintenance: add 'unregister --force'
125
126
"git maintenance unregister" in a repository that is already been
127
unregistered reported an error.
128
92
- Will merge to 'next'?
93
- source: <pull.1358.v2.git.1663853837.gitgitgadget@gmail.com>
129
+ Will merge to 'next'.
130
+ source: <pull.1358.v4.git.1664287021.gitgitgadget@gmail.com>
131
132
133
* jk/clone-allow-bare-and-o-together (2022-09-22) 1 commit
97
- - clone: allow "--bare" with "-o"
134
+ (merged to 'next' on 2022-09-27 at 1feca721ac)
135
+ + clone: allow "--bare" with "-o"
136
137
"git clone" did not like to see the "--bare" and the "--origin"
138
options used together without a good reason.
139
102
- Will merge to 'next'.
140
+ Will cook in 'next'.
141
source: <YyvzVdfQVdysvMp2@coredump.intra.peff.net>
142
143
144
* jk/fsck-on-diet (2022-09-22) 3 commits
107
- - parse_object_buffer(): respect save_commit_buffer
108
- - fsck: turn off save_commit_buffer
109
- - fsck: free tree buffers after walking unreachable objects
145
+ (merged to 'next' on 2022-09-27 at c2e93082a1)
146
+ + parse_object_buffer(): respect save_commit_buffer
147
+ + fsck: turn off save_commit_buffer
148
+ + fsck: free tree buffers after walking unreachable objects
149
150
"git fsck" failed to release contents of tree objects already used
151
from the memory, which has been fixed.
152
114
- Will merge to 'next'.
153
+ Will cook in 'next'.
154
source: <Yyw0PSVe3YTQGgRS@coredump.intra.peff.net>
155
156
157
* jk/remote-rename-without-fetch-refspec (2022-09-22) 1 commit
119
- - remote: handle rename of remote without fetch refspec
158
+ (merged to 'next' on 2022-09-27 at 165fe0a832)
159
+ + remote: handle rename of remote without fetch refspec
160
161
"git remote rename" failed to rename a remote without fetch
162
refspec, which has been corrected.
163
124
- Will merge to 'next'.
164
+ Will cook in 'next'.
165
source: <YyvzqZ5tmI0UdRAW@coredump.intra.peff.net>
166
167
128
-* js/merge-ort-in-read-only-repo (2022-09-22) 1 commit
168
+* js/merge-ort-in-read-only-repo (2022-09-26) 2 commits
169
+ - merge-ort: return early when failing to write a blob
170
- merge-ort: fix segmentation fault in read-only repositories
171
172
In read-only repositories, "git merge-tree" tried to come up with a
@@ -133,55 +174,47 @@ Release tarballs are available at:
174
led to a segfault (which is bad), which has been corrected.
175
176
Expecting a reroll.
136
- cf. <916o55op-qpqo-5o41-931s-8q54p7301sr2@tzk.qr>
137
- source: <pull.1362.v3.git.1663875999939.gitgitgadget@gmail.com>
177
+ cf. <CABPp-BGJueKtcdvzGWH_ZK6yeA6r3457ue5Uub9_gdU5M-WmvQ@mail.gmail.com>
178
+ The proposed log message for the second step may need updating.
179
+ source: <pull.1362.v4.git.1664229348.gitgitgadget@gmail.com>
180
181
182
* mc/cred-helper-ignore-unknown (2022-09-22) 3 commits
141
- - osxkeychain: clarify that we ignore unknown lines
142
- - netrc: ignore unknown lines (do not die)
143
- - wincred: ignore unknown lines (do not die)
183
+ (merged to 'next' on 2022-09-27 at ce6e3616aa)
184
+ + osxkeychain: clarify that we ignore unknown lines
185
+ + netrc: ignore unknown lines (do not die)
186
+ + wincred: ignore unknown lines (do not die)
187
188
Most credential helpers ignored unknown entries in a credential
189
description, but a few died upon seeing them. The latter were
190
taught to ignore them, too
191
149
- Will merge to 'next'?
192
+ Will cook in 'next'.
193
source: <pull.1363.git.1663865974.gitgitgadget@gmail.com>
194
195
153
-* ds/bitmap-lookup-remove-tracing (2022-09-23) 2 commits
154
- - SQUASH???
155
- - pack-bitmap: remove trace2 region from hot path
156
-
157
- Perf-fix?
158
-
159
- Expecting a reroll.
160
- cf. <edf25c5d-06f4-0b91-6773-f4fe7705c2f8@github.com>
161
- source: <pull.1365.git.1663938034607.gitgitgadget@gmail.com>
162
-
163
-
196
* es/retire-efgrep (2022-09-23) 2 commits
165
- - check-non-portable-shell: detect obsolescent egrep/fgrep
166
- - Merge branch 'dd/retire-efgrep' into es/retire-efgrep
197
+ (merged to 'next' on 2022-09-27 at 344fdd138e)
198
+ + check-non-portable-shell: detect obsolescent egrep/fgrep
199
+ + Merge branch 'dd/retire-efgrep' into es/retire-efgrep
200
(this branch uses dd/retire-efgrep.)
201
202
Prepare for GNU [ef]grep that throw warning of their uses.
203
171
- Will merge to 'next'.
204
+ Will cook in 'next'.
205
source: <pull.1338.git.git.1663805905554.gitgitgadget@gmail.com>
206
207
208
* cw/submodule-status-in-parallel (2022-09-23) 4 commits
176
- . diff-lib: parallelize run_diff_files for submodules
177
- . diff-lib: refactor functions
178
- . submodule: move status parsing into function
179
- . run-command: add pipe_output to run_processes_parallel
209
+ - diff-lib: parallelize run_diff_files for submodules
210
+ - diff-lib: refactor functions
211
+ - submodule: move status parsing into function
212
+ - run-command: add pipe_output to run_processes_parallel
213
214
Allow the internal "diff-files" engine to run "how has this
215
submodule changed?" in parallel to speed up "git status".
216
184
- Needs review.
217
+ Breaks its self check.
218
cf. https://github.com/git/git/actions/runs/3115673002/jobs/5052804463
219
source: <20220922232947.631309-1-calvinwan@google.com>
220
@@ -192,53 +225,11 @@ Release tarballs are available at:
225
The codepath that reads from the index v4 had unaligned memory
226
accesses, which has been corrected.
227
195
- Expecting a reroll?
228
+ Expecting a reroll.
229
cf. <Yy4nkEnhuzt2iH+R@coredump.intra.peff.net>
230
+ cf. <bb3a2470-7ff5-e4a6-040a-96e0e3833978@gmail.com>
231
source: <pull.1366.git.1663962236069.gitgitgadget@gmail.com>
232
199
---------------------------------------------------
200
-[Stalled]
201
-
202
-* es/mark-gc-cruft-as-experimental (2022-08-03) 2 commits
203
- - config: let feature.experimental imply gc.cruftPacks=true
204
- - gc: add tests for --cruft and friends
205
-
206
- Enable gc.cruftpacks by default for those who opt into
207
- feature.experimental setting.
208
-
209
- Expecting a reroll.
210
- cf. <220804.86a68ke9d5.gmgdl@evledraar.gmail.com>
211
- cf. <6803b725-526e-a1c8-f15c-a9ed4a144d4c@github.com>
212
- source: <20220803205721.3686361-1-emilyshaffer@google.com>
213
-
214
-
215
-* es/doc-creation-factor-fix (2022-07-28) 2 commits
216
- - range-diff: clarify --creation-factor=<factor>
217
- - format-patch: clarify --creation-factor=<factor>
218
-
219
- Expecting a reroll by somebody more familiar with the logic
220
- cf. <xmqqo7wfix7p.fsf@gitster.g>
221
- source: <7229p500-p2r4-on87-6802-8o90s36rr3s4@tzk.qr>
222
-
223
-
224
-* cw/remote-object-info (2022-08-13) 7 commits
225
- - SQUASH???
226
- - cat-file: add remote-object-info to batch-command
227
- - transport: add client support for object-info
228
- - serve: advertise object-info feature
229
- - protocol-caps: initialization bug fix
230
- - fetch-pack: move fetch initialization
231
- - fetch-pack: refactor packet writing
232
-
233
- A client component to talk with the object-info endpoint.
234
-
235
- Expecting a reroll.
236
- cf. <20220728230210.2952731-1-calvinwan@google.com>
237
- cf. <CAFySSZDvgwbbHCHfyuaqX3tKsr-GjJ9iihygg6rNNe46Ys7_EA@mail.gmail.com>
238
- source: <20220728230210.2952731-1-calvinwan@google.com>
239
-
240
---------------------------------------------------
241
-[Cooking]
233
234
* dd/retire-efgrep (2022-09-21) 4 commits
235
(merged to 'next' on 2022-09-21 at 22bc339be1)
@@ -293,30 +284,35 @@ Release tarballs are available at:
284
source: <20220914193102.5275-1-sorganov@gmail.com>
285
286
296
-* ja/rebase-i-avoid-amending-self (2022-09-21) 2 commits
297
- - SQUASH??? resurrect previous version of the tests
287
+* ja/rebase-i-avoid-amending-self (2022-09-26) 1 commit
288
- sequencer: avoid dropping fixup commit that targets self via commit-ish
289
290
"git rebase -i" can mistakenly attempt to apply a fixup to a commit
291
itself, which has been corrected.
292
303
- Does not seem to pass its own test.
304
- source: <20220920031140.1220220-1-aclopte@gmail.com>
293
+ Will merge to 'next'?
294
+ source: <20220924222904.1784975-1-aclopte@gmail.com>
295
296
297
* ac/fuzzers (2022-09-19) 1 commit
298
- fuzz: reorganise the path for existing oss-fuzz fuzzers
299
300
+ Source file shuffling.
301
+
302
+ Will merge to 'next'?
303
source: <pull.1353.v4.git.1663598215154.gitgitgadget@gmail.com>
304
305
306
* hn/parse-worktree-ref (2022-09-19) 1 commit
307
- refs: unify parse_worktree_ref() and ref_type()
308
309
+ Code and semantics cleaning.
310
+
311
+ Will merge to 'next'?
312
source: <pull.1325.v2.git.git.1663605291172.gitgitgadget@gmail.com>
313
314
319
-* ed/fsmonitor-on-networked-macos (2022-09-21) 6 commits
315
+* ed/fsmonitor-on-networked-macos (2022-09-25) 6 commits
316
- fsmonitor: add documentation for allowRemote and socketDir options
317
- fsmonitor: check for compatability before communicating with fsmonitor
318
- fsmonitor: deal with synthetic firmlinks on macOS
@@ -328,7 +324,7 @@ Release tarballs are available at:
324
filesystem is disabled. Add knobs to make it workable on macOS.
325
326
Will merge to 'next'?
331
- source: <pull.1326.v10.git.1663705986.gitgitgadget@gmail.com>
327
+ source: <pull.1326.v12.git.1664048782.gitgitgadget@gmail.com>
328
329
330
* rj/branch-edit-description-with-nth-checkout (2022-09-12) 2 commits