What's cooking (2022/06 #06)
Junio C Hamano committed
Jun 17, 2022 at 17:36 UTC
4d351f52722f19a56af5291cf5b94fd4d4a97547
1 file changed
+109
-131
whats-cooking.txt
+109
-131
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
Bcc: lwn@lwn.net
3
-Subject: What's cooking in git.git (Jun 2022, #05; Thu, 16)
4
-X-master-at: 3b9a5a33c2986522736d484da497ccd99d715220
5
-X-next-at: 10f37bed90c8150629a8f2f8f37966f953baf262
3
+Subject: What's cooking in git.git (Jun 2022, #06; Fri, 17)
4
+X-master-at: 5b71c59bc3b9365075e2a175aa7b6f2b0c84ce44
5
+X-next-at: 763f9739486ebf52dadb6c56742daf07e738829f
6
7
-What's cooking in git.git (Jun 2022, #05; Thu, 16)
7
+What's cooking in git.git (Jun 2022, #06; Fri, 17)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -13,7 +13,7 @@ topic is stable enough to be used and are candidate to be in a
13
future release). Commits prefixed with '-' are only in 'seen',
14
and aren't considered "accepted" at all.
15
16
-The first -rc for this cycle is expected to be tagged tomorrow.
16
+Git 2.37-rc1 has been tagged.
17
18
Copies of the source code to Git live in many repositories, and the
19
following is a list of the ones I push into or their mirrors. Some
@@ -44,43 +44,31 @@ Release tarballs are available at:
44
https://www.kernel.org/pub/software/scm/git/
45
46
--------------------------------------------------
47
-[Graduated to 'master']
48
-
49
-* fs/ssh-default-key-command-doc (2022-06-08) 1 commit
50
- (merged to 'next' on 2022-06-10 at b5cc5b6619)
51
- + gpg docs: explain better use of ssh.defaultKeyCommand
47
+[New Topics]
48
53
- Doc update.
54
- source: <20220608152437.126276-1-fs@gigacodes.de>
49
+* cr/setup-bug-typo (2022-06-17) 1 commit
50
+ (merged to 'next' on 2022-06-17 at 8834ffe0ab)
51
+ + setup: fix function name in a BUG() message
52
53
+ Typofix in a BUG() message.
54
57
-* jc/revert-show-parent-info (2022-05-31) 2 commits
58
- (merged to 'next' on 2022-06-07 at e405211ff4)
59
- + revert: --reference should apply only to 'revert', not 'cherry-pick'
60
- (merged to 'next' on 2022-05-30 at b5da52dc14)
61
- + revert: optionally refer to commit in the "reference" format
55
+ Will cook in 'next'.
56
+ source: <pull.1255.git.1654782920256.gitgitgadget@gmail.com>
57
63
- "git revert" learns "--reference" option to use more human-readable
64
- reference to the commit it reverts in the message template it
65
- prepares for the user.
66
- source: <xmqq8rqn7buk.fsf_-_@gitster.g>
58
59
+* zk/push-use-bitmaps (2022-06-17) 1 commit
60
+ - send-pack.c: add config push.useBitmaps
61
69
-* po/rebase-preserve-merges (2022-06-06) 4 commits
70
- (merged to 'next' on 2022-06-10 at 471f67aebc)
71
- + rebase: translate a die(preserve-merges) message
72
- + rebase: note `preserve` merges may be a pull config option
73
- + rebase: help users when dying with `preserve-merges`
74
- + rebase.c: state preserve-merges has been removed
62
+ "git push" sometimes perform poorly when reachability bitmaps are
63
+ used, even in a repository where other operations are helped by
64
+ bitmaps. The push.useBitmaps configuration variable is introduced
65
+ to allow disabling use of reachability bitmaps only for "git push".
66
76
- Various error messages that talk about the removal of
77
- "--preserve-merges" in "rebase" have been strengthened, and "rebase
78
- --abort" learned to get out of a state that was left by an earlier
79
- use of the option.
80
- source: <pull.1242.v2.git.1654341469.gitgitgadget@gmail.com>
67
+ Will merge to 'next'?
68
+ source: <pull.1263.v4.git.1655492779228.gitgitgadget@gmail.com>
69
70
--------------------------------------------------
83
-[New Topics]
71
+[Graduated to 'master']
72
73
* ab/credentials-in-url-more (2022-06-15) 2 commits
74
(merged to 'next' on 2022-06-16 at de19b3b40c)
@@ -90,11 +78,20 @@ Release tarballs are available at:
78
Rename fetch.credentialsInUrl to transfer.credentialsInUrl as the
79
single configuration variable should work both in pushing and
80
fetching.
93
-
94
- Will merge to 'master'.
81
source: <cover-0.2-00000000000-20220615T103852Z-avarab@gmail.com>
82
83
84
+* cb/path-owner-check-with-sudo-plus (2022-06-17) 1 commit
85
+ (merged to 'next' on 2022-06-17 at 518afcbc48)
86
+ + git-compat-util: allow root to access both SUDO_UID and root owned
87
+
88
+ "sudo git foo" used to consider a repository owned by the original
89
+ user a safe one to access; it now also considers a repository owned
90
+ by root a safe one, too (after all, if an attacker can craft a
91
+ malicious repository owned by root, the box is 0wned already).
92
+ source: <20220617202338.27984-1-carenas@gmail.com>
93
+
94
+
95
* ds/more-test-coverage (2022-06-16) 4 commits
96
(merged to 'next' on 2022-06-16 at 3f0452418c)
97
+ cache-tree: remove cache_tree_find_path()
@@ -103,34 +100,23 @@ Release tarballs are available at:
100
+ t2107: test 'git update-index --verbose'
101
102
Improve test coverage with a handful of tests.
106
-
107
- Will merge to 'master'.
103
source: <pull.1261.v2.git.1655385230.gitgitgadget@gmail.com>
104
105
111
-* jk/remote-show-with-negative-refspecs (2022-06-15) 1 commit
112
- - remote: handle negative refspecs in git remote show
113
-
114
- "git remote show [-n] frotz" now pays attention to negative
115
- pathspecs.
116
- source: <20220614003251.16765-1-jacob.e.keller@intel.com>
117
-
118
-
119
-* js/commit-graph-parsing-without-repo-settings (2022-06-15) 1 commit
120
- - commit-graph: refactor to avoid prepare_repo_settings
121
-
122
- source: <9b56496b0809cc8a25af877ea97042e2cb7f2af6.1655246092.git.steadmon@google.com>
106
+* jc/cocci-cleanup (2022-06-07) 1 commit
107
+ (merged to 'next' on 2022-06-16 at 990576f5c5)
108
+ + cocci: retire is_null_sha1() rule
109
110
+ Remove a coccinelle rule that is no longer relevant.
111
+ source: <xmqq7d5suoqt.fsf@gitster.g>
112
125
-* jk/optim-promisor-object-enumeration (2022-06-16) 1 commit
126
- (merged to 'next' on 2022-06-16 at ce0712a74c)
127
- + is_promisor_object(): walk promisor packs in pack-order
113
129
- Collection of what is referenced by objects in promisor packs have
130
- been optimized to inspect these objects in the in-pack order.
114
+* jk/bug-fl-va-list-fix (2022-06-16) 1 commit
115
+ (merged to 'next' on 2022-06-16 at 8150aebb0f)
116
+ + bug_fl(): correctly initialize trace2 va_list
117
132
- Will cook in 'next'.
133
- source: <YqrTsbXbEjx0Pabn@coredump.intra.peff.net>
118
+ Fix buggy va_list usage in recent code.
119
+ source: <YquMyakxYnU6mI5a@coredump.intra.peff.net>
120
121
122
* jk/perf-lib-test-titles (2022-06-16) 1 commit
@@ -138,11 +124,21 @@ Release tarballs are available at:
124
+ perf-lib: fix missing test titles in output
125
126
Show test titles to the performance test output again.
141
-
142
- Will merge to 'master'.
127
source: <YqrXLO5oMYeOr2PB@coredump.intra.peff.net>
128
129
130
+* js/ci-github-workflow-markup (2022-06-13) 3 commits
131
+ (merged to 'next' on 2022-06-15 at 03eb5e68ed)
132
+ + ci(github): also mark up compile errors
133
+ + ci(github): use grouping also in the `win-build` job
134
+ + ci(github): bring back the 'print test failures' step
135
+
136
+ Recent CI update hides certain failures in test jobs, which has
137
+ been corrected.
138
+
139
+ source: <pull.1253.v2.git.1655125988.gitgitgadget@gmail.com>
140
+
141
+
142
* js/misc-fixes (2022-06-16) 6 commits
143
(merged to 'next' on 2022-06-16 at 2f1f98e403)
144
+ relative_url(): fix incorrect condition
@@ -153,30 +149,8 @@ Release tarballs are available at:
149
+ fsmonitor: avoid memory leak in `fsm_settings__get_incompatible_msg()`
150
151
Assorted fixes to problems found by Coverity.
156
-
157
- Will merge to 'master'.
152
source: <pull.1264.git.1655336146.gitgitgadget@gmail.com>
153
160
-
161
-* ro/mktree-allow-missing-fix (2022-06-16) 1 commit
162
- - mktree: do not load objects under '--missing'
163
-
164
- "git mktree --missing" lazily fetched objects that are missing from
165
- the local object store, which was totally unnecessary.
166
-
167
- Waiting for review response.
168
- source: <1566aed1-a38f-a9ca-241c-21b56d732328@roku.com>
169
-
170
-
171
-* jk/bug-fl-va-list-fix (2022-06-16) 1 commit
172
- (merged to 'next' on 2022-06-16 at 8150aebb0f)
173
- + bug_fl(): correctly initialize trace2 va_list
174
-
175
- Fix buggy va_list usage in recent code.
176
-
177
- Will merge to 'master'.
178
- source: <YquMyakxYnU6mI5a@coredump.intra.peff.net>
179
-
154
--------------------------------------------------
155
[Stalled]
156
@@ -240,6 +214,44 @@ Release tarballs are available at:
214
--------------------------------------------------
215
[Cooking]
216
217
+* jk/remote-show-with-negative-refspecs (2022-06-17) 1 commit
218
+ - remote: handle negative refspecs in git remote show
219
+ (this branch is used by jk/t5505-restructure.)
220
+
221
+ "git remote show [-n] frotz" now pays attention to negative
222
+ pathspecs.
223
+
224
+ Will merge to 'next'?
225
+ source: <20220617002036.1577-2-jacob.keller@gmail.com>
226
+
227
+
228
+* js/commit-graph-parsing-without-repo-settings (2022-06-15) 1 commit
229
+ - commit-graph: refactor to avoid prepare_repo_settings
230
+
231
+ source: <9b56496b0809cc8a25af877ea97042e2cb7f2af6.1655246092.git.steadmon@google.com>
232
+
233
+
234
+* jk/optim-promisor-object-enumeration (2022-06-16) 1 commit
235
+ (merged to 'next' on 2022-06-16 at ce0712a74c)
236
+ + is_promisor_object(): walk promisor packs in pack-order
237
+
238
+ Collection of what is referenced by objects in promisor packs have
239
+ been optimized to inspect these objects in the in-pack order.
240
+
241
+ Will cook in 'next'.
242
+ source: <YqrTsbXbEjx0Pabn@coredump.intra.peff.net>
243
+
244
+
245
+* ro/mktree-allow-missing-fix (2022-06-16) 1 commit
246
+ - mktree: do not load objects under '--missing'
247
+
248
+ "git mktree --missing" lazily fetched objects that are missing from
249
+ the local object store, which was totally unnecessary.
250
+
251
+ Waiting for review response.
252
+ source: <1566aed1-a38f-a9ca-241c-21b56d732328@roku.com>
253
+
254
+
255
* jc/apply-icase-tests (2022-06-13) 1 commit
256
- t4141: test "git apply" with core.ignorecase
257
@@ -262,18 +274,19 @@ Release tarballs are available at:
274
275
276
* rs/archive-with-internal-gzip (2022-06-15) 6 commits
265
- - archive-tar: use internal gzip by default
266
- - archive-tar: use OS_CODE 3 (Unix) for internal gzip
267
- - archive-tar: add internal gzip implementation
268
- - archive-tar: factor out write_block()
269
- - archive: rename archiver data field to filter_command
270
- - archive: update format documentation
277
+ (merged to 'next' on 2022-06-17 at ab5af6acd1)
278
+ + archive-tar: use internal gzip by default
279
+ + archive-tar: use OS_CODE 3 (Unix) for internal gzip
280
+ + archive-tar: add internal gzip implementation
281
+ + archive-tar: factor out write_block()
282
+ + archive: rename archiver data field to filter_command
283
+ + archive: update format documentation
284
285
Teach "git archive" to (optionally and then by default) avoid
286
spawning an external "gzip" process when creating ".tar.gz" (and
287
".tgz") archives.
288
276
- Will merge to 'next'.
289
+ Will cook in 'next'.
290
source: <9df761c3-355a-ede9-7971-b32687fe9abb@web.de>
291
292
@@ -291,34 +304,22 @@ Release tarballs are available at:
304
305
306
* ds/branch-checked-out (2022-06-15) 5 commits
294
- - branch: fix branch_checked_out() leaks
295
- - branch: use branch_checked_out() when deleting refs
296
- - fetch: use new branch_checked_out() and add tests
297
- - branch: check for bisects and rebases
298
- - branch: add branch_checked_out() helper
307
+ (merged to 'next' on 2022-06-17 at c881874257)
308
+ + branch: fix branch_checked_out() leaks
309
+ + branch: use branch_checked_out() when deleting refs
310
+ + fetch: use new branch_checked_out() and add tests
311
+ + branch: check for bisects and rebases
312
+ + branch: add branch_checked_out() helper
313
314
Introduce a helper to see if a branch is already being worked on
315
(hence should not be newly checked out in a working tree), which
316
performs much better than the existing find_shared_symref() to
317
replace many uses of the latter.
318
305
- Will merge to 'next'.
319
+ Will cook in 'next'.
320
source: <pull.1254.v2.git.1655234853.gitgitgadget@gmail.com>
321
322
309
-* js/ci-github-workflow-markup (2022-06-13) 3 commits
310
- (merged to 'next' on 2022-06-15 at 03eb5e68ed)
311
- + ci(github): also mark up compile errors
312
- + ci(github): use grouping also in the `win-build` job
313
- + ci(github): bring back the 'print test failures' step
314
-
315
- Recent CI update hides certain failures in test jobs, which has
316
- been corrected.
317
-
318
- Will merge to 'master'?
319
- source: <pull.1253.v2.git.1655125988.gitgitgadget@gmail.com>
320
-
321
-
323
* jt/connected-show-missing-from-which-side (2022-06-10) 1 commit
324
- fetch,fetch-pack: clarify connectivity check error
325
@@ -359,7 +360,7 @@ Release tarballs are available at:
360
The resolve-undo information in the index was not protected against
361
GC, which has been corrected.
362
362
- Will merge to 'master'?
363
+ Will cook in 'next'.
364
source: <xmqqfskdieqz.fsf@gitster.g>
365
366
@@ -371,7 +372,7 @@ Release tarballs are available at:
372
373
Bash command line prompt (in contrib/) update.
374
374
- Will merge to 'master'?
375
+ Will merge to 'master'.
376
source: <20220607115024.64724-1-joak-pet@online.no>
377
378
@@ -447,16 +448,6 @@ Release tarballs are available at:
448
source: <cover.1654552560.git.me@ttaylorr.com>
449
450
450
-* jc/cocci-cleanup (2022-06-07) 1 commit
451
- (merged to 'next' on 2022-06-16 at 990576f5c5)
452
- + cocci: retire is_null_sha1() rule
453
-
454
- Remove a coccinelle rule that is no longer relevant.
455
-
456
- Will merge to 'master'.
457
- source: <xmqq7d5suoqt.fsf@gitster.g>
458
-
459
-
451
* ds/bundle-uri-more (2022-06-06) 6 commits
452
- fetch: add 'refs/bundle/' to log.excludeDecoration
453
- bundle-uri: add support for http(s):// and file://
@@ -495,19 +486,6 @@ Release tarballs are available at:
486
source: <pull.1132.v3.git.1653144546.gitgitgadget@gmail.com>
487
488
498
-* cb/path-owner-check-with-sudo-plus (2022-05-12) 1 commit
499
- - git-compat-util: allow root to access both SUDO_UID and root owned
500
-
501
- "sudo git foo" used to consider a repository owned by the original
502
- user a safe one to access; it now also considers a repository owned
503
- by root a safe one, too (after all, if an attacker can craft a
504
- malicious repository owned by root, the box is 0wned already).
505
-
506
- Will merge to 'next'?
507
- cf. <20220519152344.ktrifm3pc42bjruh@Carlos-MacBook-Pro-2.local>
508
- source: <20220513010020.55361-5-carenas@gmail.com>
509
-
510
-
489
* gc/bare-repo-discovery (2022-06-07) 5 commits
490
- setup.c: create `discovery.bare`
491
- safe.directory: use git_protected_config()