What's cooking (2022/09 #07)
Junio C Hamano committed
Sep 23, 2022 at 16:03 UTC
a187d1abd19e813e7fdcfc6972f0e8f37b6eaab3
1 file changed
+157
-121
whats-cooking.txt
+157
-121
@@ -1,9 +1,9 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Sep 2022, #06; Wed, 21)
3
-X-master-at: 1b3d6e17fe83eb6f79ffbac2f2c61bbf1eaef5f8
4
-X-next-at: 413fe02c70ffea5b779d4f98dfa4a502e54bc4ab
2
+Subject: What's cooking in git.git (Sep 2022, #07; Fri, 23)
3
+X-master-at: 4fd6c5e44459e6444c2cd93383660134c95aabd1
4
+X-next-at: ed0d419d3c1a574b86ddc99554cdd663ffe0f5be
5
6
-What's cooking in git.git (Sep 2022, #06; Wed, 21)
6
+What's cooking in git.git (Sep 2022, #07; Fri, 23)
7
--------------------------------------------------
8
9
Here are the topics that have been cooking in my tree. Commits
@@ -13,10 +13,16 @@ 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-rc1 has been tagged. Now the 'master' branch is in the
17
-"regression fixes only" mode (cf. https://tinyurl.com/gitCal) until
18
-the final release. I may start dropping patches on a completely new
19
-topics that has no relevance on the upcoming release.
16
+The -rc1 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).
26
27
Copies of the source code to Git live in many repositories, and the
28
following is a list of the ones I push into or their mirrors. Some
@@ -49,153 +55,146 @@ Release tarballs are available at:
55
--------------------------------------------------
56
[Graduated to 'master']
57
52
-* ec/reftable-pass-pq-entry-by-reference (2022-09-15) 1 commit
53
- (merged to 'next' on 2022-09-15 at 928e75c7d1)
54
- + reftable: use a pointer for pq_entry param
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
61
56
- Small code clean-up in reftable implementation.
57
- source: <1833f3928cb.acf3c97d869879.7909589521159235166@elijahpepe.com>
62
+ Grammofix.
63
+ source: <20220922025158.415969-1-alexhenrie24@gmail.com>
64
65
60
-* fz/help-doublofix (2022-09-16) 1 commit
61
- (merged to 'next' on 2022-09-19 at 3ec5906f4e)
62
- + help: fix doubled words in explanation for developer interfaces
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
69
64
- Typofix for topic already in -rc0.
65
- source: <pull.1330.git.git.1663333529294.gitgitgadget@gmail.com>
70
+ Fix uninitialized memory access in a recent fix-up that is already
71
+ in -rc1.
72
+ source: <YywsZU9UUoC08UcN@coredump.intra.peff.net>
73
74
68
-* js/typofix (2022-09-21) 2 commits
69
- (merged to 'next' on 2022-09-21 at bb2082c5ef)
70
- + Documentation: clean up various typos in technical docs
71
- + Documentation: clean up a few misspelled word typos
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
78
73
- Will merge to 'master'.
74
- source: <20220920024557.22889-1-jacob@initialcommit.io>
79
+ Fix manpage generation.
80
+ source: <20220923080733.1995862-1-martin.agren@gmail.com>
81
82
+--------------------------------------------------
83
+[New Topics]
84
77
-* ml/commit-graph-expire-dir-leak-fix (2022-09-19) 1 commit
78
- (merged to 'next' on 2022-09-19 at e3211e888e)
79
- + commit-graph: Fix missing closedir in expire_commit_graphs
85
+* ds/scalar-unregister-idempotent (2022-09-22) 2 commits
86
+ - scalar: make 'unregister' idempotent
87
+ - maintenance: add 'unregister --force'
88
81
- A result from opendir() was leaking in the commit-graph expiration
82
- codepath, which has been plugged.
83
- source: <20220919141441.5644-1-linmq006@gmail.com>
89
+ "git maintenance unregister" in a repository that is already been
90
+ unregistered reported an error.
91
92
+ Will merge to 'next'?
93
+ source: <pull.1358.v2.git.1663853837.gitgitgadget@gmail.com>
94
86
-* sg/clean-test-results (2022-09-21) 1 commit
87
- (merged to 'next' on 2022-09-21 at 15e66ceb37)
88
- + t/Makefile: remove 'test-results' on 'make clean'
95
90
- "make clean" stopped cleaning the test results directory as a side
91
- effect of a topic that has nothing to do with "make clean", which
92
- has been corrected.
93
- source: <20220920201619.40972-1-szeder.dev@gmail.com>
96
+* jk/clone-allow-bare-and-o-together (2022-09-22) 1 commit
97
+ - clone: allow "--bare" with "-o"
98
99
+ "git clone" did not like to see the "--bare" and the "--origin"
100
+ options used together without a good reason.
101
96
-* sg/parse-options-subcommand (2022-09-21) 1 commit
97
- (merged to 'next' on 2022-09-21 at 42650aa5f1)
98
- + gc: don't translate literal commands
102
+ Will merge to 'next'.
103
+ source: <YyvzVdfQVdysvMp2@coredump.intra.peff.net>
104
100
- Fix messages incorrectly marked for translation.
101
- source: <20220920050725.326383-1-alexhenrie24@gmail.com>
105
106
+* 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
110
104
-* tz/tech-docs-to-help-fix (2022-09-16) 2 commits
105
- (merged to 'next' on 2022-09-19 at 4a13143da1)
106
- + api docs: link to html version of api-trace2
107
- + docs: fix a few recently broken links
111
+ "git fsck" failed to release contents of tree objects already used
112
+ from the memory, which has been fixed.
113
109
- Docfix for topic already in -rc0.
110
- source: <20220916062303.3736166-2-tmz@pobox.com>
114
+ Will merge to 'next'.
115
+ source: <Yyw0PSVe3YTQGgRS@coredump.intra.peff.net>
116
117
113
-* vd/check-docs-fixes (2022-09-19) 2 commits
114
- (merged to 'next' on 2022-09-21 at 549e699018)
115
- + version: fix builtin linking & documentation
116
- + diagnose: add to command-list.txt
118
+* jk/remote-rename-without-fetch-refspec (2022-09-22) 1 commit
119
+ - remote: handle rename of remote without fetch refspec
120
118
- Build fix.
119
- source: <pull.1360.git.1663633195.gitgitgadget@gmail.com>
121
+ "git remote rename" failed to rename a remote without fetch
122
+ refspec, which has been corrected.
123
124
+ Will merge to 'next'.
125
+ source: <YyvzqZ5tmI0UdRAW@coredump.intra.peff.net>
126
122
-* vd/doc-reviewing-guidelines (2022-09-19) 1 commit
123
- (merged to 'next' on 2022-09-21 at c30f77dbe6)
124
- + Documentation: add ReviewingGuidelines
127
126
- Just like we have coding guidelines, we now have guidelines for
127
- reviewers.
128
- source: <pull.1348.v2.git.1663614767058.gitgitgadget@gmail.com>
128
+* js/merge-ort-in-read-only-repo (2022-09-22) 1 commit
129
+ - merge-ort: fix segmentation fault in read-only repositories
130
131
+ In read-only repositories, "git merge-tree" tried to come up with a
132
+ merge result tree object, which it failed (which is not wrong) and
133
+ led to a segfault (which is bad), which has been corrected.
134
131
-* vd/scalar-generalize-diagnose (2022-09-21) 2 commits
132
- (merged to 'next' on 2022-09-21 at 1102451ebd)
133
- + builtin/diagnose.c: don't translate the two mode values
134
- (merged to 'next' on 2022-09-19 at e03e8a6e4a)
135
- + diagnose.c: refactor to safely use 'd_type'
135
+ Expecting a reroll.
136
+ cf. <916o55op-qpqo-5o41-931s-8q54p7301sr2@tzk.qr>
137
+ source: <pull.1362.v3.git.1663875999939.gitgitgadget@gmail.com>
138
137
- Portability fix.
138
- source: <pull.1354.git.1663438615413.gitgitgadget@gmail.com>
139
- source: <20220920050632.326307-1-alexhenrie24@gmail.com>
139
141
---------------------------------------------------
142
-[New Topics]
140
+* 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)
144
144
-* dd/retire-efgrep (2022-09-21) 4 commits
145
- (merged to 'next' on 2022-09-21 at 22bc339be1)
146
- + t: convert fgrep usage to "grep -F"
147
- + t: convert egrep usage to "grep -E"
148
- + t: remove \{m,n\} from BRE grep usage
149
- + CodingGuidelines: allow grep -E
145
+ Most credential helpers ignored unknown entries in a credential
146
+ description, but a few died upon seeing them. The latter were
147
+ taught to ignore them, too
148
151
- Prepare for GNU [ef]grep that throw warning of their uses.
149
+ Will merge to 'next'?
150
+ source: <pull.1363.git.1663865974.gitgitgadget@gmail.com>
151
153
- Will cook in 'next'.
154
- source: <cover.1663765176.git.congdanhqx@gmail.com>
152
153
+* ds/bitmap-lookup-remove-tracing (2022-09-23) 2 commits
154
+ - SQUASH???
155
+ - pack-bitmap: remove trace2 region from hot path
156
157
-* ds/maintenance-unregsiter-ignore-missing (2022-09-21) 1 commit
158
- - maintenance: make unregister idempotent
157
+ Perf-fix?
158
160
- "git maintenance unregister" in a repository that is already been
161
- unregistered reported an error.
159
+ Expecting a reroll.
160
+ cf. <edf25c5d-06f4-0b91-6773-f4fe7705c2f8@github.com>
161
+ source: <pull.1365.git.1663938034607.gitgitgadget@gmail.com>
162
163
- Somewhat dubious?
164
- cf. <xmqqpmfo4pc7.fsf@gitster.g>
165
- source: <pull.1358.git.1663635732095.gitgitgadget@gmail.com>
163
164
+* 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
167
+ (this branch uses dd/retire-efgrep.)
168
168
-* tb/midx-repack-ignore-cruft-packs (2022-09-21) 7 commits
169
- - midx.c: avoid cruft packs with non-zero `repack --batch-size`
170
- - midx.c: remove unnecessary loop condition
171
- - midx.c: replace `xcalloc()` with `CALLOC_ARRAY()`
172
- - midx.c: avoid cruft packs with `repack --batch-size=0`
173
- - midx.c: prevent `expire` from removing the cruft pack
174
- - Documentation/git-multi-pack-index.txt: clarify expire behavior
175
- - Documentation/git-multi-pack-index.txt: fix typo
169
+ Prepare for GNU [ef]grep that throw warning of their uses.
170
177
- source: <cover.1663638929.git.me@ttaylorr.com>
171
+ Will merge to 'next'.
172
+ source: <pull.1338.git.git.1663805905554.gitgitgadget@gmail.com>
173
174
180
-* ah/fsmonitor-daemon-usage-non-l10n (2022-09-21) 1 commit
181
- (merged to 'next' on 2022-09-21 at bc69a73c6c)
182
- + fsmonitor--daemon: don't translate literal commands
175
+* 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
180
184
- Fix messages incorrectly marked for translation.
181
+ Allow the internal "diff-files" engine to run "how has this
182
+ submodule changed?" in parallel to speed up "git status".
183
186
- Will cook in 'next'.
187
- source: <20220920050709.326359-1-alexhenrie24@gmail.com>
184
+ Needs review.
185
+ cf. https://github.com/git/git/actions/runs/3115673002/jobs/5052804463
186
+ source: <20220922232947.631309-1-calvinwan@google.com>
187
188
190
-* js/merge-tree-in-read-only-repo (2022-09-21) 1 commit
191
- - merge-tree: fix segmentation fault in read-only repositories
189
+* vd/fix-unaligned-read-index-v4 (2022-09-23) 1 commit
190
+ - read-cache: avoid misaligned reads in index v4
191
193
- In read-only repositories, "git merge-tree" tried to come up with a
194
- merge result tree object, which it failed (which is not wrong) and
195
- led to a segfault (which is bad), which has been corrected.
192
+ The codepath that reads from the index v4 had unaligned memory
193
+ accesses, which has been corrected.
194
197
- Will merge to 'next'.
198
- source: <pull.1362.v2.git.1663798083240.gitgitgadget@gmail.com>
195
+ Expecting a reroll?
196
+ cf. <Yy4nkEnhuzt2iH+R@coredump.intra.peff.net>
197
+ source: <pull.1366.git.1663962236069.gitgitgadget@gmail.com>
198
199
--------------------------------------------------
200
[Stalled]
@@ -241,14 +240,56 @@ Release tarballs are available at:
240
--------------------------------------------------
241
[Cooking]
242
243
+* dd/retire-efgrep (2022-09-21) 4 commits
244
+ (merged to 'next' on 2022-09-21 at 22bc339be1)
245
+ + t: convert fgrep usage to "grep -F"
246
+ + t: convert egrep usage to "grep -E"
247
+ + t: remove \{m,n\} from BRE grep usage
248
+ + CodingGuidelines: allow grep -E
249
+ (this branch is used by es/retire-efgrep.)
250
+
251
+ Prepare for GNU [ef]grep that throw warning of their uses.
252
+
253
+ Will cook in 'next'.
254
+ source: <cover.1663765176.git.congdanhqx@gmail.com>
255
+
256
+
257
+* tb/midx-repack-ignore-cruft-packs (2022-09-21) 7 commits
258
+ - midx.c: avoid cruft packs with non-zero `repack --batch-size`
259
+ - midx.c: remove unnecessary loop condition
260
+ - midx.c: replace `xcalloc()` with `CALLOC_ARRAY()`
261
+ - midx.c: avoid cruft packs with `repack --batch-size=0`
262
+ - midx.c: prevent `expire` from removing the cruft pack
263
+ - Documentation/git-multi-pack-index.txt: clarify expire behavior
264
+ - Documentation/git-multi-pack-index.txt: fix typo
265
+
266
+ "git multi-pack-index repack/expire" used to repack unreachable
267
+ cruft into a new pack, which have been corrected.
268
+
269
+ Will merge to 'next'?
270
+ cf. <63a1c3d4-eff3-af10-4263-058c88e74594@github.com>
271
+ source: <cover.1663638929.git.me@ttaylorr.com>
272
+
273
+
274
+* ah/fsmonitor-daemon-usage-non-l10n (2022-09-21) 1 commit
275
+ (merged to 'next' on 2022-09-21 at bc69a73c6c)
276
+ + fsmonitor--daemon: don't translate literal commands
277
+
278
+ Fix messages incorrectly marked for translation.
279
+
280
+ Will cook in 'next'.
281
+ source: <20220920050709.326359-1-alexhenrie24@gmail.com>
282
+
283
+
284
* so/diff-merges-cleanup (2022-09-16) 3 commits
245
- - diff-merges: clarify log.diffMerges documentation
246
- - diff-merges: cleanup set_diff_merges()
247
- - diff-merges: cleanup func_by_opt()
285
+ (merged to 'next' on 2022-09-22 at 57694bbed7)
286
+ + diff-merges: clarify log.diffMerges documentation
287
+ + diff-merges: cleanup set_diff_merges()
288
+ + diff-merges: cleanup func_by_opt()
289
290
Code clean-up.
291
251
- Will merge to 'next'?
292
+ Will cook in 'next'.
293
source: <20220914193102.5275-1-sorganov@gmail.com>
294
295
@@ -434,17 +475,12 @@ Release tarballs are available at:
475
source: <pull.1321.git.git.1661806456.gitgitgadget@gmail.com>
476
477
437
-* sy/sparse-grep (2022-09-08) 3 commits
438
- - builtin/grep.c: walking tree instead of expanding index with --sparse
478
+* sy/sparse-grep (2022-09-23) 1 commit
479
- builtin/grep.c: integrate with sparse index
440
- - builtin/grep.c: add --sparse option
441
-
442
- "git grep" learned to work better in a sparse checkout.
480
444
- The design of "--sparse" feels iffy.
445
- cf. <093827ae-41ef-5f7c-7829-647536ce1305@github.com>
446
- cf. <CABPp-BF-z72=hY_Jf8h3g95s+wwZOsV_S=+dDNs_AVskQxoaTw@mail.gmail.com>
447
- source: <20220908001854.206789-1-shaoxuan.yuan02@gmail.com>
481
+ "git grep" learned to expand the sparse-index more lazily and on
482
+ demand in a sparse checkout.
483
+ source: <20220923041842.27817-2-shaoxuan.yuan02@gmail.com>
484
485
486
* ds/use-platform-regex-on-macos (2022-08-26) 1 commit