What's cooking (2022/09 #06)
Junio C Hamano committed
Sep 21, 2022 at 16:03 UTC
2aec5765247f83052c6ac926ca53deb75d4dce8c
1 file changed
+151
-160
whats-cooking.txt
+151
-160
@@ -1,9 +1,9 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Sep 2022, #05; Mon, 19)
3
-X-master-at: dda7228a83e2e9ff584bf6adbf55910565b41e14
4
-X-next-at: 39d753a26bd0c11658343a9e4366f68cd11f7781
2
+Subject: What's cooking in git.git (Sep 2022, #06; Wed, 21)
3
+X-master-at: 1b3d6e17fe83eb6f79ffbac2f2c61bbf1eaef5f8
4
+X-next-at: 413fe02c70ffea5b779d4f98dfa4a502e54bc4ab
5
6
-What's cooking in git.git (Sep 2022, #05; Mon, 19)
6
+What's cooking in git.git (Sep 2022, #06; Wed, 21)
7
--------------------------------------------------
8
9
Here are the topics that have been cooking in my tree. Commits
@@ -13,12 +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
-A few more topics have been merged to the 'master' branch. We plan
17
-to tag -rc1 in a few days (but expect no movement on 'master' or
18
-'next' tomorrow). There are a few topics that are marked with the
19
-"Merge to 'next'?" marker, which can use your help ;-) After -rc1
20
-gets tagged, the 'master' branch will go in the "regression fixes
21
-only" mode (cf. https://tinyurl.com/gitCal).
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.
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
@@ -51,121 +49,56 @@ Release tarballs are available at:
49
--------------------------------------------------
50
[Graduated to 'master']
51
54
-* ad/t1800-cygwin (2022-09-15) 1 commit
55
- (merged to 'next' on 2022-09-15 at 9667abb48c)
56
- + t1800: correct test to handle Cygwin
57
-
58
- Test fix.
59
- source: <20220915075717.425673-1-adam@dinwoodie.org>
60
-
61
-
62
-* es/chainlint (2022-09-12) 19 commits
63
- (merged to 'next' on 2022-09-12 at 577e59143f)
64
- + chainlint: colorize problem annotations and test delimiters
65
- (merged to 'next' on 2022-09-08 at eab3357b05)
66
- + t: retire unused chainlint.sed
67
- + t/Makefile: teach `make test` and `make prove` to run chainlint.pl
68
- + test-lib: replace chainlint.sed with chainlint.pl
69
- + test-lib: retire "lint harder" optimization hack
70
- + t/chainlint: add more chainlint.pl self-tests
71
- + chainlint.pl: allow `|| echo` to signal failure upstream of a pipe
72
- + chainlint.pl: complain about loops lacking explicit failure handling
73
- + chainlint.pl: don't flag broken &&-chain if failure indicated explicitly
74
- + chainlint.pl: don't flag broken &&-chain if `$?` handled explicitly
75
- + chainlint.pl: don't require `&` background command to end with `&&`
76
- + t/Makefile: apply chainlint.pl to existing self-tests
77
- + chainlint.pl: don't require `return|exit|continue` to end with `&&`
78
- + chainlint.pl: validate test scripts in parallel
79
- + chainlint.pl: add parser to identify test definitions
80
- + chainlint.pl: add parser to validate tests
81
- + chainlint.pl: add POSIX shell parser
82
- + chainlint.pl: add POSIX shell lexical analyzer
83
- + t: add skeleton chainlint.pl
84
-
85
- Revamp chainlint script for our tests.
86
- source: <pull.1322.git.git.1661992197.gitgitgadget@gmail.com>
87
- source: <pull.1324.git.git.1663023888412.gitgitgadget@gmail.com>
88
-
89
-
90
-* jk/list-objects-filter-cleanup (2022-09-12) 5 commits
91
- (merged to 'next' on 2022-09-12 at 33cb79c924)
92
- + list-objects-filter: convert filter_spec to a strbuf
93
- + list-objects-filter: add and use initializers
94
- + list-objects-filter: handle null default filter spec
95
- + list-objects-filter: don't memset after releasing filter struct
96
- + Merge branch 'jk/plug-list-object-filter-leaks' into jk/list-objects-filter-cleanup
97
-
98
- A couple of bugfixes with code clean-up.
99
- source: <Yx1qwlpNbxGEiUgc@coredump.intra.peff.net>
100
-
101
-
102
-* sy/mv-out-of-cone (2022-09-09) 10 commits
103
- (merged to 'next' on 2022-09-12 at 7cb7b41779)
104
- + builtin/mv.c: fix possible segfault in add_slash()
105
- (merged to 'next' on 2022-08-17 at 2316d9ce4d)
106
- + mv: check overwrite for in-to-out move
107
- + advice.h: add advise_on_moving_dirty_path()
108
- + mv: cleanup empty WORKING_DIRECTORY
109
- + mv: from in-cone to out-of-cone
110
- + mv: remove BOTH from enum update_mode
111
- + mv: check if <destination> is a SKIP_WORKTREE_DIR
112
- + mv: free the with_slash in check_dir_in_index()
113
- + mv: rename check_dir_in_index() to empty_dir_has_sparse_contents()
114
- + t7002: add tests for moving from in-cone to out-of-cone
115
-
116
- "git mv A B" in a sparsely populated working tree can be asked to
117
- move a path from a directory that is "in cone" to another directory
118
- that is "out of cone". Handling of such a case has been improved.
119
- source: <20220809120910.2021413-1-shaoxuan.yuan02@gmail.com>
120
- source: <20220909222736.279362-1-shaoxuan.yuan02@gmail.com>
121
-
122
-
123
-* vd/scalar-to-main (2022-09-02) 9 commits
124
- (merged to 'next' on 2022-09-14 at 230bf89c01)
125
- + Documentation/technical: include Scalar technical doc
126
- + t/perf: add 'GIT_PERF_USE_SCALAR' run option
127
- + t/perf: add Scalar performance tests
128
- + scalar-clone: add test coverage
129
- + scalar: add to 'git help -a' command list
130
- + scalar: implement the `help` subcommand
131
- + git help: special-case `scalar`
132
- + scalar: include in standard Git build & installation
133
- + scalar: fix command documentation section header
134
-
135
- Hoist the remainder of "scalar" out of contrib/ to the main part of
136
- the codebase.
137
- source: <pull.1341.v2.git.1662134210.gitgitgadget@gmail.com>
138
-
139
-
140
-* zh/ls-files-format (2022-09-12) 1 commit
141
- (merged to 'next' on 2022-09-12 at 91dda58387)
142
- + ls-files: fix black space in error message
143
-
144
- Typofix in the UI of a topic that has graduated to 'master'.
145
- source: <pull.1350.git.1662904997760.gitgitgadget@gmail.com>
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
55
+
56
+ Small code clean-up in reftable implementation.
57
+ source: <1833f3928cb.acf3c97d869879.7909589521159235166@elijahpepe.com>
58
147
---------------------------------------------------
148
-[New Topics]
59
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
63
64
Typofix for topic already in -rc0.
65
+ source: <pull.1330.git.git.1663333529294.gitgitgadget@gmail.com>
66
+
67
+
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
72
73
Will merge to 'master'.
157
- source: <pull.1330.git.git.1663333529294.gitgitgadget@gmail.com>
74
+ source: <20220920024557.22889-1-jacob@initialcommit.io>
75
76
160
-* so/diff-merges-cleanup (2022-09-16) 3 commits
161
- - diff-merges: clarify log.diffMerges documentation
162
- - diff-merges: cleanup set_diff_merges()
163
- - diff-merges: cleanup func_by_opt()
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
80
165
- Code clean-up.
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>
84
+
85
+
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'
89
+
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>
94
167
- Will merge to 'next'?
168
- source: <20220914193102.5275-1-sorganov@gmail.com>
95
+
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
99
+
100
+ Fix messages incorrectly marked for translation.
101
+ source: <20220920050725.326383-1-alexhenrie24@gmail.com>
102
103
104
* tz/tech-docs-to-help-fix (2022-09-16) 2 commits
@@ -174,52 +107,95 @@ Release tarballs are available at:
107
+ docs: fix a few recently broken links
108
109
Docfix for topic already in -rc0.
177
-
178
- Will merge to 'master'.
110
source: <20220916062303.3736166-2-tmz@pobox.com>
111
112
182
-* ja/rebase-i-avoid-amending-self (2022-09-19) 1 commit
183
- - sequencer: avoid dropping fixup commit that targets self via commit-ish
184
-
185
- "git rebase -i" can mistakenly attempt to apply a fixup to a commit
186
- itself, which has been corrected.
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
117
188
- Will merge to 'next'?
189
- source: <20220918121053.880225-1-aclopte@gmail.com>
118
+ Build fix.
119
+ source: <pull.1360.git.1663633195.gitgitgadget@gmail.com>
120
121
192
-* ml/commit-graph-expire-dir-leak-fix (2022-09-19) 1 commit
193
- (merged to 'next' on 2022-09-19 at e3211e888e)
194
- + commit-graph: Fix missing closedir in expire_commit_graphs
195
-
196
- A result from opendir() was leaking in the commit-graph expiration
197
- codepath, which has been plugged.
122
+* vd/doc-reviewing-guidelines (2022-09-19) 1 commit
123
+ (merged to 'next' on 2022-09-21 at c30f77dbe6)
124
+ + Documentation: add ReviewingGuidelines
125
199
- Will merge to 'master'.
200
- source: <20220919141441.5644-1-linmq006@gmail.com>
126
+ Just like we have coding guidelines, we now have guidelines for
127
+ reviewers.
128
+ source: <pull.1348.v2.git.1663614767058.gitgitgadget@gmail.com>
129
130
203
-* vd/scalar-generalize-diagnose (2022-09-19) 1 commit
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'
136
137
Portability fix.
208
-
209
- Will merge to 'master'.
138
source: <pull.1354.git.1663438615413.gitgitgadget@gmail.com>
139
+ source: <20220920050632.326307-1-alexhenrie24@gmail.com>
140
141
+--------------------------------------------------
142
+[New Topics]
143
213
-* ac/fuzzers (2022-09-19) 1 commit
214
- - fuzz: reorganise the path for existing oss-fuzz fuzzers
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
150
216
- source: <pull.1353.v4.git.1663598215154.gitgitgadget@gmail.com>
151
+ Prepare for GNU [ef]grep that throw warning of their uses.
152
153
+ Will cook in 'next'.
154
+ source: <cover.1663765176.git.congdanhqx@gmail.com>
155
219
-* hn/parse-worktree-ref (2022-09-19) 1 commit
220
- - refs: unify parse_worktree_ref() and ref_type()
156
222
- source: <pull.1325.v2.git.git.1663605291172.gitgitgadget@gmail.com>
157
+* ds/maintenance-unregsiter-ignore-missing (2022-09-21) 1 commit
158
+ - maintenance: make unregister idempotent
159
+
160
+ "git maintenance unregister" in a repository that is already been
161
+ unregistered reported an error.
162
+
163
+ Somewhat dubious?
164
+ cf. <xmqqpmfo4pc7.fsf@gitster.g>
165
+ source: <pull.1358.git.1663635732095.gitgitgadget@gmail.com>
166
+
167
+
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
176
+
177
+ source: <cover.1663638929.git.me@ttaylorr.com>
178
+
179
+
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
183
+
184
+ Fix messages incorrectly marked for translation.
185
+
186
+ Will cook in 'next'.
187
+ source: <20220920050709.326359-1-alexhenrie24@gmail.com>
188
+
189
+
190
+* js/merge-tree-in-read-only-repo (2022-09-21) 1 commit
191
+ - merge-tree: fix segmentation fault in read-only repositories
192
+
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.
196
+
197
+ Will merge to 'next'.
198
+ source: <pull.1362.v2.git.1663798083240.gitgitgadget@gmail.com>
199
200
--------------------------------------------------
201
[Stalled]
@@ -265,8 +241,43 @@ Release tarballs are available at:
241
--------------------------------------------------
242
[Cooking]
243
268
-* ed/fsmonitor-on-networked-macos (2022-09-19) 5 commits
244
+* 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()
248
+
249
+ Code clean-up.
250
+
251
+ Will merge to 'next'?
252
+ source: <20220914193102.5275-1-sorganov@gmail.com>
253
+
254
+
255
+* ja/rebase-i-avoid-amending-self (2022-09-21) 2 commits
256
+ - SQUASH??? resurrect previous version of the tests
257
+ - sequencer: avoid dropping fixup commit that targets self via commit-ish
258
+
259
+ "git rebase -i" can mistakenly attempt to apply a fixup to a commit
260
+ itself, which has been corrected.
261
+
262
+ Does not seem to pass its own test.
263
+ source: <20220920031140.1220220-1-aclopte@gmail.com>
264
+
265
+
266
+* ac/fuzzers (2022-09-19) 1 commit
267
+ - fuzz: reorganise the path for existing oss-fuzz fuzzers
268
+
269
+ source: <pull.1353.v4.git.1663598215154.gitgitgadget@gmail.com>
270
+
271
+
272
+* hn/parse-worktree-ref (2022-09-19) 1 commit
273
+ - refs: unify parse_worktree_ref() and ref_type()
274
+
275
+ source: <pull.1325.v2.git.git.1663605291172.gitgitgadget@gmail.com>
276
+
277
+
278
+* ed/fsmonitor-on-networked-macos (2022-09-21) 6 commits
279
- fsmonitor: add documentation for allowRemote and socketDir options
280
+ - fsmonitor: check for compatability before communicating with fsmonitor
281
- fsmonitor: deal with synthetic firmlinks on macOS
282
- fsmonitor: avoid socket location check if using hook
283
- fsmonitor: relocate socket file if .git directory is remote
@@ -276,7 +287,7 @@ Release tarballs are available at:
287
filesystem is disabled. Add knobs to make it workable on macOS.
288
289
Will merge to 'next'?
279
- source: <pull.1326.v8.git.1663377141.gitgitgadget@gmail.com>
290
+ source: <pull.1326.v10.git.1663705986.gitgitgadget@gmail.com>
291
292
293
* rj/branch-edit-description-with-nth-checkout (2022-09-12) 2 commits
@@ -305,16 +316,6 @@ Release tarballs are available at:
316
source: <pull.1352.git.1663097156.gitgitgadget@gmail.com>
317
318
308
-* ec/reftable-pass-pq-entry-by-reference (2022-09-15) 1 commit
309
- (merged to 'next' on 2022-09-15 at 928e75c7d1)
310
- + reftable: use a pointer for pq_entry param
311
-
312
- Small code clean-up in reftable implementation.
313
-
314
- Will merge to 'master'.
315
- source: <1833f3928cb.acf3c97d869879.7909589521159235166@elijahpepe.com>
316
-
317
-
319
* jc/environ-docs (2022-09-16) 5 commits
320
- environ: GIT_INDEX_VERSION affects not just a new repository
321
- environ: simplify description of GIT_INDEX_FILE
@@ -388,16 +389,6 @@ Release tarballs are available at:
389
source: <cover-00.34-00000000000-20220902T092734Z-avarab@gmail.com>
390
391
391
-* vd/doc-reviewing-guidelines (2022-09-19) 1 commit
392
- - Documentation: add ReviewingGuidelines
393
-
394
- Just like we have coding guidelines, we now have guidelines for
395
- reviewers.
396
-
397
- Will merge to 'next' and then to 'master'.
398
- source: <pull.1348.v2.git.1663614767058.gitgitgadget@gmail.com>
399
-
400
-
392
* ab/coccicheck-incremental (2022-08-31) 9 commits
393
- spatchcache: add a ccache-alike for "spatch"
394
- cocci: optimistically use COMPUTE_HEADER_DEPENDENCIES