What's cooking (2024/02 #06)
Junio C Hamano committed
Feb 15, 2024 at 16:21 UTC
3230a854c10fcb4686db033544f75088d8352e82
1 file changed
+197
-243
whats-cooking.txt
+197
-243
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Feb 2024, #05; Tue, 13)
3
-X-master-at: 2996f11c1d11ab68823f0939b6469dedc2b9ab90
4
-X-next-at: d0d6417c1e3e625e276a94050391e37766a706c2
2
+Subject: What's cooking in git.git (Feb 2024, #06; Thu, 15)
3
+X-master-at: 3e0d3cd5c7def4808247caf168e17f2bbf47892b
4
+X-next-at: 4c4623230009152fbd5fe219d2adafef26b50c0f
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Feb 2024, #05; Tue, 13)
7
+What's cooking in git.git (Feb 2024, #06; Thu, 15)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -17,9 +17,9 @@ topic without enough support may be discarded after a long period of
17
no activity (of course they can be resubmit when new interests
18
arise).
19
20
-Git 2.44-rc1 will be tagged soon. This round, let's try having just
21
-one release candidate before the final, which is expected to be
22
-tagged on or around 20th.
20
+Git 2.44-rc1 has been tagged. This round, let's try having just one
21
+release candidate before the final, which is expected to be tagged
22
+on or around 20th.
23
24
Copies of the source code to Git live in many repositories, and the
25
following is a list of the ones I push into or their mirrors. Some
@@ -50,165 +50,112 @@ Release tarballs are available at:
50
https://www.kernel.org/pub/software/scm/git/
51
52
--------------------------------------------------
53
-[Graduated to 'master']
54
-
55
-* bk/complete-bisect (2024-02-06) 7 commits
56
- (merged to 'next' on 2024-02-07 at ac95a595b7)
57
- + completion: bisect: recognize but do not complete view subcommand
58
- + completion: bisect: complete log opts for visualize subcommand
59
- + completion: new function __git_complete_log_opts
60
- + completion: bisect: complete missing --first-parent and - -no-checkout options
61
- + completion: bisect: complete custom terms and related options
62
- + completion: bisect: complete bad, new, old, and help subcommands
63
- + completion: tests: always use 'master' for default initial branch name
53
+[New Topics]
54
65
- Command line completion support (in contrib/) has been
66
- updated for "git bisect".
67
- source: <20240206215048.488344-1-britton.kerin@gmail.com>
55
+* jh/fsmonitor-icase-corner-case-fix (2024-02-14) 11 commits
56
+ - t7527: update case-insenstive fsmonitor test
57
+ - fsmonitor: refactor bit invalidation in refresh callback
58
+ - fsmonitor: support case-insensitive non-directory events
59
+ - fsmonitor: refactor non-directory callback
60
+ - fsmonitor: support case-insensitive directory events
61
+ - fsmonitor: refactor untracked-cache invalidation
62
+ - fsmonitor: clarify handling of directory events in callback
63
+ - fsmonitor: refactor refresh callback for non-directory events
64
+ - fsmonitor: refactor refresh callback on directory events
65
+ - t7527: add case-insensitve test for FSMonitor
66
+ - name-hash: add index_dir_exists2()
67
+
68
+ FSMonitor client code was confused when FSEvents were given in a
69
+ different case on a case-insensitive filesystem, which has been
70
+ corrected.
71
72
+ Needs review.
73
+ source: <pull.1662.git.1707857541.gitgitgadget@gmail.com>
74
70
-* jc/bisect-doc (2024-02-07) 2 commits
71
- (merged to 'next' on 2024-02-07 at 914fa6775f)
72
- + bisect: document command line arguments for "bisect start"
73
- + bisect: document "terms" subcommand more fully
75
75
- Doc update.
76
- source: <20240207214436.538586-1-gitster@pobox.com>
76
+* mh/credential-oauth-refresh-token-with-osxkeychain (2024-02-14) 1 commit
77
+ - credential/osxkeychain: store new attributes
78
79
+ OAuth refresh tokens and password expiry timestamps are now stored
80
+ in the osxkeychain backend , just the way libsecret and wincred
81
+ backends of the credential subsystem do.
82
79
-* jc/sign-buffer-failure-propagation-fix (2024-02-07) 2 commits
80
- (merged to 'next' on 2024-02-08 at badb96b5ac)
81
- + ssh signing: signal an error with a negative return value
82
- (merged to 'next' on 2024-02-07 at 2cedac9d38)
83
- + tag: fix sign_buffer() call to create a signed tag
83
+ Needs testing.
84
+ cf. <CAGJzqsmSzMqEG1OU9dH6CORV6=L7qUAFNJSmi41Lqrajf9mSew@mail.gmail.com>
85
+ source: <pull.1663.git.1707860618119.gitgitgadget@gmail.com>
86
85
- A failed "git tag -s" did not necessarily result in an error
86
- depending on the crypto backend, which has been corrected.
87
- source: <xmqq4jek9ko1.fsf@gitster.g>
88
- source: <xmqq5xyzr6tm.fsf@gitster.g>
87
88
+* ps/reftable-iteration-perf-part2 (2024-02-14) 13 commits
89
+ - reftable: allow inlining of a few functions
90
+ - reftable/record: decode keys in place
91
+ - reftable/record: reuse refname when copying
92
+ - reftable/record: reuse refname when decoding
93
+ - reftable/merged: avoid duplicate pqueue emptiness check
94
+ - reftable/merged: circumvent pqueue with single subiter
95
+ - reftable/merged: handle subiter cleanup on close only
96
+ - reftable/merged: remove unnecessary null check for subiters
97
+ - reftable/merged: make subiters own their records
98
+ - reftable/merged: advance subiter on subsequent iteration
99
+ - reftable/merged: make `merged_iter` structure private
100
+ - reftable/pq: use `size_t` to track iterator index
101
+ - Merge branch 'ps/reftable-iteration-perf' into ps/reftable-iteration-perf-part2
102
+ (this branch uses ps/reftable-iteration-perf.)
103
91
-* pb/template-for-single-commit-pr (2024-02-06) 1 commit
92
- (merged to 'next' on 2024-02-07 at 2a56c8eb13)
93
- + .github/PULL_REQUEST_TEMPLATE.md: add a note about single-commit PRs
104
+ The code to iterate over refs with the reftable backend has seen
105
+ some optimization.
106
95
- Doc update.
96
- source: <pull.1665.v2.git.git.1707225612576.gitgitgadget@gmail.com>
107
+ Needs review.
108
+ source: <cover.1707895758.git.ps@pks.im>
109
110
99
-* ps/reftable-multi-level-indices-fix (2024-02-01) 6 commits
100
- (merged to 'next' on 2024-02-07 at 143f47a079)
101
- + reftable: document reading and writing indices
102
- + reftable/writer: fix writing multi-level indices
103
- + reftable/writer: simplify writing index records
104
- + reftable/writer: use correct type to iterate through index entries
105
- + reftable/reader: be more careful about errors in indexed seeks
106
- + Merge branch 'jc/reftable-core-fsync' into ps/reftable-multi-level-indices-fix
111
+* cp/t9146-use-test-path-helpers (2024-02-14) 1 commit
112
+ - t9146: replace test -d/-e/-f with appropriate test_path_is_* function
113
108
- Write multi-level indices for reftable has been corrected.
109
- source: <cover.1706773842.git.ps@pks.im>
114
+ Test script clean-up.
115
+ source: <pull.1661.v3.git.1707933048210.gitgitgadget@gmail.com>
116
117
112
-* ps/reftable-styles (2024-02-06) 9 commits
113
- (merged to 'next' on 2024-02-07 at 18670512e2)
114
- + reftable/record: improve semantics when initializing records
115
- + reftable/merged: refactor initialization of iterators
116
- + reftable/merged: refactor seeking of records
117
- + reftable/stack: use `size_t` to track stack length
118
- + reftable/stack: use `size_t` to track stack slices during compaction
119
- + reftable/stack: index segments with `size_t`
120
- + reftable/stack: fix parameter validation when compacting range
121
- + reftable: introduce macros to allocate arrays
122
- + reftable: introduce macros to grow arrays
118
+* rj/tag-column-fix (2024-02-14) 1 commit
119
+ - tag: error when git-column fails
120
124
- Code clean-up in various reftable code paths.
125
- source: <cover.1707200355.git.ps@pks.im>
121
+ "git tag --column" failed to check the exit status of its "git
122
+ column" invocation, which has been corrected.
123
124
+ Will merge to 'next'?
125
+ source: <59df085d-0de8-45b1-9b8b-c69e91e56a1f@gmail.com>
126
128
-* ps/report-failure-from-git-stash (2024-02-06) 1 commit
129
- (merged to 'next' on 2024-02-07 at a8a3f91f61)
130
- + builtin/stash: report failure to write to index
127
132
- "git stash" sometimes was silent even when it failed due to
133
- unwritable index file, which has been corrected.
134
- source: <cb098cf88cbfcbf7c4872f8887856629b909cb91.1707197653.git.ps@pks.im>
128
+* jc/am-whitespace-doc (2024-02-14) 1 commit
129
+ - doc: add shortcut to "am --whitespace=<action>"
130
131
+ "git am --help" now tells readers what actions are available in
132
+ "git am --whitespace=<action>", in addition to saying that the
133
+ option is passed through to the underlying "git apply".
134
137
-* pw/show-ref-pseudorefs (2024-02-07) 2 commits
138
- (merged to 'next' on 2024-02-08 at 7e9f850dba)
139
- + t1400: use show-ref to check pseudorefs
140
- + show-ref --verify: accept pseudorefs
135
+ Will merge to 'next'?
136
+ source: <xmqqplwyvqby.fsf@gitster.g>
137
142
- "git show-ref --verify" did not show things like "CHERRY_PICK_HEAD",
143
- which has been corrected.
144
- source: <pull.1654.git.1707324277.gitgitgadget@gmail.com>
138
139
+* ba/credential-test-clean-fix (2024-02-15) 1 commit
140
+ - t/lib-credential: clean additional credential
141
147
-* tb/multi-pack-reuse-experiment (2024-02-05) 2 commits
148
- (merged to 'next' on 2024-02-08 at e92afaa170)
149
- + pack-objects: enable multi-pack reuse via `feature.experimental`
150
- + t5332-multi-pack-reuse.sh: extract pack-objects helper functions
142
+ Test clean-up.
143
152
- Setting `feature.experimental` opts the user into multi-pack reuse
153
- experiment
144
+ Will merge to 'next'?
145
+ source: <pull.1664.git.1707959036807.gitgitgadget@gmail.com>
146
155
- Will cook in 'next'.
156
- source: <cover.1707173415.git.me@ttaylorr.com>
147
148
+* js/cmake-with-test-tool (2024-02-15) 1 commit
149
+ - cmake: let `test-tool` run the unit tests, too
150
+ (this branch uses js/unit-test-suite-runner.)
151
159
-* vd/for-each-ref-sort-with-formatted-timestamp (2024-02-07) 1 commit
160
- (merged to 'next' on 2024-02-08 at 5f86cad208)
161
- + ref-filter.c: sort formatted dates by byte value
152
+ "test-tool" is now built in CMake build to also run the unit tests.
153
163
- "git branch" and friends learned to use the formatted text as
164
- sorting key, not the underlying timestamp value, when the --sort
165
- option is used with author or committer timestamp with a format
166
- specifier (e.g., "--sort=creatordate:format:%H:%M:%S").
167
- source: <pull.1655.git.1707357439586.gitgitgadget@gmail.com>
154
+ May want to roll it into the base topic.
155
+ source: <cover.1706921262.git.steadmon@google.com>
156
157
--------------------------------------------------
170
-[New Topics]
171
-
172
-* ps/ref-tests-update-even-more (2024-02-09) 7 commits
173
- - t7003: ensure filter-branch prunes reflogs with the reftable backend
174
- - t2011: exercise D/F conflicts with HEAD with the reftable backend
175
- - t1405: remove unneeded cleanup step
176
- - t1404: make D/F conflict tests compatible with reftable backend
177
- - t1400: exercise reflog with gaps with reftable backend
178
- - t0410: enable tests with extensions with non-default repo format
179
- - t: move tests exercising the "files" backend
180
-
181
- More tests that are marked as "ref-files only" have been updated to
182
- improve test coverage of reftable backend.
183
-
184
- Needs review.
185
- source: <cover.1707463221.git.ps@pks.im>
186
-
187
-
188
-* pw/gc-during-rebase (2024-02-09) 1 commit
189
- (merged to 'next' on 2024-02-12 at d54c5ce325)
190
- + prune: mark rebase autostash and orig-head as reachable
191
-
192
- The sequencer machinery does not use the ref API and instead
193
- records names of certain objects it needs for its correct operation
194
- in temporary files, which makes these objects susceptible to loss
195
- by garbage collection. These temporary files have been added as
196
- starting points for reachability analysis to fix this.
197
-
198
- Will merge to 'master'.
199
- source: <pull.1656.v2.git.1707495579886.gitgitgadget@gmail.com>
200
-
201
-
202
-* rs/receive-pack-remove-find-header (2024-02-12) 2 commits
203
- (merged to 'next' on 2024-02-12 at f1bf281e10)
204
- + receive-pack: use find_commit_header() in check_nonce()
205
- + receive-pack: use find_commit_header() in check_cert_push_options()
206
-
207
- Code simplification.
208
-
209
- Will merge to 'master'.
210
- source: <8b350cae-2180-4ac7-a911-d40043576445@web.de>
211
-
158
+[Graduated to 'master']
159
160
* cp/git-flush-is-an-env-bool (2024-02-13) 1 commit
161
(merged to 'next' on 2024-02-13 at c0850f5675)
@@ -222,6 +169,19 @@ Release tarballs are available at:
169
source: <xmqqbk8k5eo0.fsf@gitster.g>
170
171
172
+* jc/github-actions-update (2024-02-02) 3 commits
173
+ (merged to 'next' on 2024-02-07 at 2cd6caaf70)
174
+ + Merge branch 'jc/maint-github-actions-update' into jc/github-actions-update
175
+ + GitHub Actions: update to github-script@v7
176
+ + GitHub Actions: update to checkout@v4
177
+ (this branch is used by js/github-actions-update.)
178
+
179
+ Squelch node.js 16 deprecation warnings from GitHub Actions CI
180
+ by updating actions/github-script and actions/checkout that use
181
+ node.js 20.
182
+ source: <20240202203935.1240458-1-gitster@pobox.com>
183
+
184
+
185
* jc/unit-tests-make-relative-fix (2024-02-12) 1 commit
186
(merged to 'next' on 2024-02-12 at 554eddef80)
187
+ unit-tests: do show relative file paths on non-Windows, too
@@ -230,11 +190,18 @@ Release tarballs are available at:
190
the unit-test machinery, assumed that the compiler expanded __FILE__
191
to the path to the source given to the $(CC), but some compilers
192
give full path, breaking the output. This has been corrected.
233
-
234
- Will merge to 'master'.
193
source: <xmqqle7r9enn.fsf_-_@gitster.g>
194
195
196
+* js/check-null-from-read-object-file (2024-02-06) 1 commit
197
+ (merged to 'next' on 2024-02-12 at 3a18369516)
198
+ + Always check the return value of `repo_read_object_file()`
199
+
200
+ The code paths that call repo_read_object_file() have been
201
+ tightened to react to errors.
202
+ source: <pull.1650.git.1707143753726.gitgitgadget@gmail.com>
203
+
204
+
205
* js/github-actions-update (2024-02-12) 2 commits
206
(merged to 'next' on 2024-02-12 at f52de8b126)
207
+ ci(linux32): add a note about Actions that must not be updated
@@ -243,11 +210,79 @@ Release tarballs are available at:
210
211
Update remaining GitHub Actions jobs to avoid warnings against
212
using deprecated version of Node.js.
246
-
247
- Will merge to 'master'.
213
source: <pull.1660.v2.git.1707653489.gitgitgadget@gmail.com>
214
215
216
+* jx/dirstat-parseopt-help (2024-02-14) 1 commit
217
+ (merged to 'next' on 2024-02-14 at 901101e5f5)
218
+ + diff: mark param1 and param2 as placeholders
219
+
220
+ The mark-up of diff options has been updated to help translators.
221
+ source: <3a82f72f33663f162aa41cb20c0fb3b6786971c9.1707900029.git.worldhello.net@gmail.com>
222
+
223
+
224
+* pb/complete-config (2024-02-12) 4 commits
225
+ (merged to 'next' on 2024-02-13 at d09f5e469a)
226
+ + completion: add and use __git_compute_second_level_config_vars_for_section
227
+ + completion: add and use __git_compute_first_level_config_vars_for_section
228
+ + completion: complete 'submodule.*' config variables
229
+ + completion: add space after config variable names also in Bash 3
230
+
231
+ The command line completion script (in contrib/) learned to
232
+ complete configuration variable names better.
233
+ cf. <Zcs34kGTqTbIana6@tanuki>
234
+ source: <pull.1660.v3.git.git.1707589943.gitgitgadget@gmail.com>
235
+
236
+
237
+* pw/gc-during-rebase (2024-02-09) 1 commit
238
+ (merged to 'next' on 2024-02-12 at d54c5ce325)
239
+ + prune: mark rebase autostash and orig-head as reachable
240
+
241
+ The sequencer machinery does not use the ref API and instead
242
+ records names of certain objects it needs for its correct operation
243
+ in temporary files, which makes these objects susceptible to loss
244
+ by garbage collection. These temporary files have been added as
245
+ starting points for reachability analysis to fix this.
246
+ source: <pull.1656.v2.git.1707495579886.gitgitgadget@gmail.com>
247
+
248
+
249
+* rs/receive-pack-remove-find-header (2024-02-12) 2 commits
250
+ (merged to 'next' on 2024-02-12 at f1bf281e10)
251
+ + receive-pack: use find_commit_header() in check_nonce()
252
+ + receive-pack: use find_commit_header() in check_cert_push_options()
253
+
254
+ Code simplification.
255
+ source: <8b350cae-2180-4ac7-a911-d40043576445@web.de>
256
+
257
+
258
+* vn/rebase-with-cherry-pick-authorship (2024-02-08) 1 commit
259
+ (merged to 'next' on 2024-02-09 at ed35d33595)
260
+ + sequencer: unset GIT_CHERRY_PICK_HELP for 'exec' commands
261
+
262
+ "git cherry-pick" invoked during "git rebase -i" session lost
263
+ the authorship information, which has been corrected.
264
+ source: <0adb1068-ef10-44ed-ad1d-e0927a09245d@gmail.com>
265
+
266
+--------------------------------------------------
267
+[Cooking]
268
+
269
+* ps/ref-tests-update-even-more (2024-02-15) 7 commits
270
+ (merged to 'next' on 2024-02-15 at 064b2b4089)
271
+ + t7003: ensure filter-branch prunes reflogs with the reftable backend
272
+ + t2011: exercise D/F conflicts with HEAD with the reftable backend
273
+ + t1405: remove unneeded cleanup step
274
+ + t1404: make D/F conflict tests compatible with reftable backend
275
+ + t1400: exercise reflog with gaps with reftable backend
276
+ + t0410: convert tests to use DEFAULT_REPO_FORMAT prereq
277
+ + t: move tests exercising the "files" backend
278
+
279
+ More tests that are marked as "ref-files only" have been updated to
280
+ improve test coverage of reftable backend.
281
+
282
+ Will cook in 'next'.
283
+ source: <cover.1707985173.git.ps@pks.im>
284
+
285
+
286
* rs/use-xstrncmpz (2024-02-12) 1 commit
287
(merged to 'next' on 2024-02-12 at 37e5f0fc14)
288
+ use xstrncmpz()
@@ -271,63 +306,56 @@ Release tarballs are available at:
306
command line, but it did not honor an empty string to mean "pass
307
everything", which has been corrected.
308
274
- Needs review.
309
+ Will merge to 'next'?
310
source: <20240211183923.131278-1-karthik.188@gmail.com>
311
312
313
* kh/column-reject-negative-padding (2024-02-13) 2 commits
279
- - column: guard against negative padding
280
- - column: disallow negative padding
314
+ (merged to 'next' on 2024-02-14 at c30c08e495)
315
+ + column: guard against negative padding
316
+ + column: disallow negative padding
317
318
"git column" has been taught to reject negative padding value, as
319
it would lead to nonsense behaviour including division by zero.
320
285
- Will merge to 'next'?
321
+ Will cook in 'next'.
322
source: <cover.1707839454.git.code@khaugsbakk.name>
323
288
---------------------------------------------------
289
-[Cooking]
290
-
291
-* vn/rebase-with-cherry-pick-authorship (2024-02-08) 1 commit
292
- (merged to 'next' on 2024-02-09 at ed35d33595)
293
- + sequencer: unset GIT_CHERRY_PICK_HELP for 'exec' commands
294
-
295
- "git cherry-pick" invoked during "git rebase -i" session lost
296
- the authorship information, which has been corrected.
297
-
298
- Will merge to 'master'.
299
- source: <0adb1068-ef10-44ed-ad1d-e0927a09245d@gmail.com>
300
-
324
325
* jc/no-lazy-fetch (2024-02-13) 1 commit
303
- - git: --no-lazy-fetch option
326
+ (merged to 'next' on 2024-02-13 at 7c7136e547)
327
+ + git: --no-lazy-fetch option
328
329
"git --no-lazy-fetch cmd" allows to run "cmd" while disabling lazy
330
fetching of objects from the promisor remote, which may be handy
331
for debugging.
332
309
- Will merge to 'next'.
333
+ May want to do the environment variable thing as well.
334
+ cf. <20240215053056.GD2821179@coredump.intra.peff.net>
335
source: <xmqq1q9mmtpw.fsf@gitster.g>
336
337
338
* jc/t9210-lazy-fix (2024-02-08) 1 commit
314
- - t9210: do not rely on lazy fetching to fail
339
+ (merged to 'next' on 2024-02-13 at fb61ca2fba)
340
+ + t9210: do not rely on lazy fetching to fail
341
+ (this branch is used by cc/rev-list-allow-missing-tips.)
342
343
Adjust use of "rev-list --missing" in an existing tests so that it
344
does not depend on a buggy failure mode.
345
319
- Will merge to 'next'.
346
+ Will cook in 'next'.
347
source: <xmqq7cjemttr.fsf@gitster.g>
348
349
350
* gt/at-is-synonym-for-head-in-add-patch (2024-02-13) 2 commits
324
- - add -p tests: remove PERL prerequisites
325
- - add-patch: classify '@' as a synonym for 'HEAD'
351
+ (merged to 'next' on 2024-02-14 at cd901555d6)
352
+ + add -p tests: remove PERL prerequisites
353
+ + add-patch: classify '@' as a synonym for 'HEAD'
354
355
Teach "git checkout -p" and friends that "@" is a synonym for
356
"HEAD".
357
330
- Will merge to 'next'?
358
+ Will cook in 'next'.
359
source: <20240211202035.7196-2-shyamthakkar001@gmail.com>
360
361
@@ -339,6 +367,7 @@ Release tarballs are available at:
367
- test-tool run-command testsuite: get shell from env
368
- t0080: turn t-basic unit test into a helper
369
- Merge branch 'jk/unit-tests-buildfix' into js/unit-test-suite-runner
370
+ (this branch is used by js/cmake-with-test-tool.)
371
372
The "test-tool" has been taught to run testsuite tests in parallel,
373
bypassing the need to use the "prove" tool.
@@ -348,17 +377,6 @@ Release tarballs are available at:
377
source: <cover.1706921262.git.steadmon@google.com>
378
379
351
-* js/check-null-from-read-object-file (2024-02-06) 1 commit
352
- (merged to 'next' on 2024-02-12 at 3a18369516)
353
- + Always check the return value of `repo_read_object_file()`
354
-
355
- The code paths that call repo_read_object_file() have been
356
- tightened to react to errors.
357
-
358
- Will merge to 'master'.
359
- source: <pull.1650.git.1707143753726.gitgitgadget@gmail.com>
360
-
361
-
380
* ps/reftable-backend (2024-02-07) 3 commits
381
(merged to 'next' on 2024-02-08 at ba1c4c52bb)
382
+ refs/reftable: fix leak when copying reflog fails
@@ -373,19 +391,19 @@ Release tarballs are available at:
391
source: <cover.1707288261.git.ps@pks.im>
392
393
376
-* cc/rev-list-allow-missing-tips (2024-02-08) 4 commits
394
+* cc/rev-list-allow-missing-tips (2024-02-14) 4 commits
395
- rev-list: allow missing tips with --missing=[print|allow*]
396
- t6022: fix 'test' style and 'even though' typo
397
- oidset: refactor oidset_insert_from_set()
398
- revision: clarify a 'return NULL' in get_reference()
399
+ (this branch uses jc/t9210-lazy-fix.)
400
401
"git rev-list --missing=print" have learned to optionally take
402
"--allow-missing-tips", which allows the objects at the starting
403
points to be missing.
404
386
- Comments?
387
- cf. <xmqq7cjemttr.fsf@gitster.g>
388
- source: <20240208135055.2705260-1-christian.couder@gmail.com>
405
+ Will merge to 'next'?
406
+ source: <20240214142513.4002639-1-christian.couder@gmail.com>
407
408
409
* ps/reftable-iteration-perf (2024-02-12) 7 commits
@@ -397,6 +415,7 @@ Release tarballs are available at:
415
+ reftable/merged: skip comparison for records of the same subiter
416
+ reftable/merged: allocation-less dropping of shadowed records
417
+ reftable/record: introduce function to compare records by key
418
+ (this branch is used by ps/reftable-iteration-perf-part2.)
419
420
The code to iterate over refs with the reftable backend has seen
421
some optimization.
@@ -405,21 +424,6 @@ Release tarballs are available at:
424
source: <cover.1707726654.git.ps@pks.im>
425
426
408
-* jc/github-actions-update (2024-02-02) 3 commits
409
- (merged to 'next' on 2024-02-07 at 2cd6caaf70)
410
- + Merge branch 'jc/maint-github-actions-update' into jc/github-actions-update
411
- + GitHub Actions: update to github-script@v7
412
- + GitHub Actions: update to checkout@v4
413
- (this branch is used by js/github-actions-update.)
414
-
415
- Squelch node.js 16 deprecation warnings from GitHub Actions CI
416
- by updating actions/github-script and actions/checkout that use
417
- node.js 20.
418
-
419
- Will merge to 'master'.
420
- source: <20240202203935.1240458-1-gitster@pobox.com>
421
-
422
-
427
* js/merge-tree-3-trees (2024-02-07) 6 commits
428
- cache-tree: avoid an unnecessary check
429
- Always check `parse_tree*()`'s return value
@@ -439,21 +443,6 @@ Release tarballs are available at:
443
source: <pull.1651.v2.git.1707324461.gitgitgadget@gmail.com>
444
445
442
-* pb/complete-config (2024-02-12) 4 commits
443
- (merged to 'next' on 2024-02-13 at d09f5e469a)
444
- + completion: add and use __git_compute_second_level_config_vars_for_section
445
- + completion: add and use __git_compute_first_level_config_vars_for_section
446
- + completion: complete 'submodule.*' config variables
447
- + completion: add space after config variable names also in Bash 3
448
-
449
- The command line completion script (in contrib/) learned to
450
- complete configuration variable names better.
451
-
452
- Will merge to 'master'.
453
- cf. <Zcs34kGTqTbIana6@tanuki>
454
- source: <pull.1660.v3.git.git.1707589943.gitgitgadget@gmail.com>
455
-
456
-
446
* rj/complete-reflog (2024-01-26) 4 commits
447
- completion: reflog show <log-options>
448
- completion: reflog with implicit "show"
@@ -631,38 +620,3 @@ Release tarballs are available at:
620
621
Not ready to be reviewed yet.
622
source: <20230824205456.1231371-1-gitster@pobox.com>
634
-
635
---------------------------------------------------
636
-[Discarded]
637
-
638
-* tb/pair-chunk-expect (2023-11-10) 8 commits
639
- . midx: read `OOFF` chunk with `pair_chunk_expect()`
640
- . midx: read `OIDL` chunk with `pair_chunk_expect()`
641
- . commit-graph: read `BIDX` chunk with `pair_chunk_expect()`
642
- . commit-graph: read `GDAT` chunk with `pair_chunk_expect()`
643
- . commit-graph: read `CDAT` chunk with `pair_chunk_expect()`
644
- . commit-graph: read `OIDL` chunk with `pair_chunk_expect()`
645
- . chunk-format: introduce `pair_chunk_expect()` helper
646
- . Merge branch 'jk/chunk-bounds-more' into HEAD
647
-
648
- Further code clean-up.
649
-
650
- Retracted for now.
651
- cf. <ZcFjkfbsBfk7JQIH@nand.local>
652
- source: <cover.1699569246.git.me@ttaylorr.com>
653
-
654
-
655
-* ak/color-decorate-symbols (2023-10-23) 7 commits
656
- - log: add color.decorate.pseudoref config variable
657
- - refs: exempt pseudorefs from pattern prefixing
658
- - refs: add pseudorefs array and iteration functions
659
- - log: add color.decorate.ref config variable
660
- - log: add color.decorate.symbol config variable
661
- - log: use designated inits for decoration_colors
662
- - config: restructure color.decorate documentation
663
-
664
- A new config for coloring.
665
-
666
- Ejected, to be rebuilt on updated kn/for-all-refs topic
667
- cf. <xmqqcyt853vz.fsf@gitster.g>
668
- source: <20231023221143.72489-1-andy.koppe@gmail.com>