What's cooking (2024/02 #05)
Junio C Hamano committed
Feb 13, 2024 at 14:22 UTC
55dcc7360b18633a45ccea1ec63678eecdeb70d3
1 file changed
+244
-226
whats-cooking.txt
+244
-226
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Feb 2024, #04; Thu, 8)
3
-X-master-at: 5216f8f5c4089ec29ce49afa147434c23e0f0163
4
-X-next-at: 5546620c9085abb7ffcf1203c4e150d0cc96ba91
2
+Subject: What's cooking in git.git (Feb 2024, #05; Tue, 13)
3
+X-master-at: 2996f11c1d11ab68823f0939b6469dedc2b9ab90
4
+X-next-at: d0d6417c1e3e625e276a94050391e37766a706c2
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Feb 2024, #04; Thu, 8)
7
+What's cooking in git.git (Feb 2024, #05; Tue, 13)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -17,10 +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
-The preview release Git 2.44-rc0 has been tagged. Let's see how
21
-well this pre-release period goes; unlike previous cycles, I planned
22
-only for one release candidate in the middle of next week until the
23
-final release around the 20th.
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.
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
@@ -53,75 +52,87 @@ Release tarballs are available at:
52
--------------------------------------------------
53
[Graduated to 'master']
54
56
-* cp/unit-test-prio-queue (2024-01-22) 1 commit
57
- (merged to 'next' on 2024-02-01 at 38aa6559b0)
58
- + tests: move t0009-prio-queue.sh to the new unit testing framework
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
64
60
- The priority queue test has been migrated to the unit testing
61
- framework.
62
- source: <pull.1642.v4.git.1705865326185.gitgitgadget@gmail.com>
65
+ Command line completion support (in contrib/) has been
66
+ updated for "git bisect".
67
+ source: <20240206215048.488344-1-britton.kerin@gmail.com>
68
69
65
-* ja/doc-placeholders-fix (2023-12-26) 2 commits
66
- (merged to 'next' on 2024-02-05 at 047da8cbb0)
67
- + doc: enforce placeholders in documentation
68
- + doc: enforce dashes in placeholders
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
74
70
- Docfix.
71
- source: <pull.1626.git.1703539287.gitgitgadget@gmail.com>
75
+ Doc update.
76
+ source: <20240207214436.538586-1-gitster@pobox.com>
77
78
74
-* jc/index-pack-fsck-levels (2024-02-01) 2 commits
75
- (merged to 'next' on 2024-02-02 at 0e4ef26aa1)
76
- + index-pack: --fsck-objects to take an optional argument for fsck msgs
77
- + index-pack: test and document --strict=<msg-id>=<severity>...
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
84
79
- The "--fsck-objects" option of "git index-pack" now can take the
80
- optional parameter to tweak severity of different fsck errors.
81
- source: <pull.1658.v4.git.git.1706751483.gitgitgadget@gmail.com>
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>
89
90
84
-* jh/sparse-index-expand-to-path-fix (2024-02-02) 1 commit
85
- (merged to 'next' on 2024-02-06 at 17ec59dd9a)
86
- + sparse-index: pass string length to index_file_exists()
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
94
88
- A caller called index_file_exists() that takes a string expressed
89
- as <ptr, length> with a wrong length, which has been corrected.
90
- source: <pull.1649.git.1706897095273.gitgitgadget@gmail.com>
95
+ Doc update.
96
+ source: <pull.1665.v2.git.git.1707225612576.gitgitgadget@gmail.com>
97
98
93
-* jk/unit-tests-buildfix (2024-02-02) 4 commits
94
- (merged to 'next' on 2024-02-02 at 8838dd21e8)
95
- + t/Makefile: say the default target upfront
96
- (merged to 'next' on 2024-01-31 at 00df31c4c8)
97
- + t/Makefile: get UNIT_TESTS list from C sources
98
- + Makefile: remove UNIT_TEST_BIN directory with "make clean"
99
- + Makefile: use mkdir_p_parent_template for UNIT_TEST_BIN
100
- (this branch is used by js/unit-test-suite-runner.)
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
107
102
- Build dependency around unit tests has been fixed.
103
- source: <20240130053714.GA165967@coredump.intra.peff.net>
104
- source: <xmqqjznmtjr9.fsf@gitster.g>
108
+ Write multi-level indices for reftable has been corrected.
109
+ source: <cover.1706773842.git.ps@pks.im>
110
111
107
-* mh/credential-oauth-refresh-token-with-wincred (2024-01-29) 1 commit
108
- (merged to 'next' on 2024-02-05 at 68880a751a)
109
- + credential/wincred: store oauth_refresh_token
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
123
111
- The wincred credential backend has been taught to support oauth refresh
112
- token the same way as credential-cache and credential-libsecret backends.
113
- source: <pull.1534.v3.git.1706477103039.gitgitgadget@gmail.com>
124
+ Code clean-up in various reftable code paths.
125
+ source: <cover.1707200355.git.ps@pks.im>
126
127
116
-* pb/imap-send-wo-curl-build-fix (2024-02-01) 1 commit
117
- (merged to 'next' on 2024-02-05 at 18368f61a7)
118
- + imap-send: add missing "strbuf.h" include under NO_CURL
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
131
120
- Build fix.
121
- source: <pull.1664.git.git.1706833113569.gitgitgadget@gmail.com>
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>
135
123
---------------------------------------------------
124
-[New Topics]
136
137
* pw/show-ref-pseudorefs (2024-02-07) 2 commits
138
(merged to 'next' on 2024-02-08 at 7e9f850dba)
@@ -130,41 +141,172 @@ Release tarballs are available at:
141
142
"git show-ref --verify" did not show things like "CHERRY_PICK_HEAD",
143
which has been corrected.
133
-
134
- Will merge to 'master'.
144
source: <pull.1654.git.1707324277.gitgitgadget@gmail.com>
145
146
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
151
+
152
+ Setting `feature.experimental` opts the user into multi-pack reuse
153
+ experiment
154
+
155
+ Will cook in 'next'.
156
+ source: <cover.1707173415.git.me@ttaylorr.com>
157
+
158
+
159
* vd/for-each-ref-sort-with-formatted-timestamp (2024-02-07) 1 commit
139
- - ref-filter.c: sort formatted dates by byte value
160
+ (merged to 'next' on 2024-02-08 at 5f86cad208)
161
+ + ref-filter.c: sort formatted dates by byte value
162
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").
145
-
146
- Will merge to 'next'.
167
source: <pull.1655.git.1707357439586.gitgitgadget@gmail.com>
168
169
+--------------------------------------------------
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
+
212
+
213
+* cp/git-flush-is-an-env-bool (2024-02-13) 1 commit
214
+ (merged to 'next' on 2024-02-13 at c0850f5675)
215
+ + write-or-die: fix the polarity of GIT_FLUSH environment variable
216
+
217
+ Recent conversion to allow more than 0/1 in GIT_FLUSH broke the
218
+ mechanism by flipping what yes/no means by mistake, which has been
219
+ corrected.
220
+
221
+ Will merge to 'master' and then to 'maint'
222
+ source: <xmqqbk8k5eo0.fsf@gitster.g>
223
+
224
+
225
+* jc/unit-tests-make-relative-fix (2024-02-12) 1 commit
226
+ (merged to 'next' on 2024-02-12 at 554eddef80)
227
+ + unit-tests: do show relative file paths on non-Windows, too
228
+
229
+ The mechanism to report the filename in the source code, used by
230
+ the unit-test machinery, assumed that the compiler expanded __FILE__
231
+ to the path to the source given to the $(CC), but some compilers
232
+ give full path, breaking the output. This has been corrected.
233
+
234
+ Will merge to 'master'.
235
+ source: <xmqqle7r9enn.fsf_-_@gitster.g>
236
+
237
+
238
+* js/github-actions-update (2024-02-12) 2 commits
239
+ (merged to 'next' on 2024-02-12 at f52de8b126)
240
+ + ci(linux32): add a note about Actions that must not be updated
241
+ + ci: bump remaining outdated Actions versions
242
+ (this branch uses jc/github-actions-update.)
243
+
244
+ Update remaining GitHub Actions jobs to avoid warnings against
245
+ using deprecated version of Node.js.
246
+
247
+ Will merge to 'master'.
248
+ source: <pull.1660.v2.git.1707653489.gitgitgadget@gmail.com>
249
+
250
+
251
+* rs/use-xstrncmpz (2024-02-12) 1 commit
252
+ (merged to 'next' on 2024-02-12 at 37e5f0fc14)
253
+ + use xstrncmpz()
254
+
255
+ Code clean-up.
256
+
257
+ Will cook in 'next'.
258
+ source: <954b75d0-1504-4f57-b34e-e770a4b7b3ea@web.de>
259
+
260
+
261
+* kn/for-all-refs (2024-02-12) 6 commits
262
+ - for-each-ref: add new option to include root refs
263
+ - ref-filter: rename 'FILTER_REFS_ALL' to 'FILTER_REFS_REGULAR'
264
+ - refs: introduce `refs_for_each_include_root_refs()`
265
+ - refs: extract out `loose_fill_ref_dir_regular_file()`
266
+ - refs: introduce `is_pseudoref()` and `is_headref()`
267
+ - Merge branch 'ps/reftable-backend' into kn/for-all-refs
268
+ (this branch uses ps/reftable-backend.)
269
+
270
+ "git for-each-ref" filters its output with prefixes given from the
271
+ command line, but it did not honor an empty string to mean "pass
272
+ everything", which has been corrected.
273
+
274
+ Needs review.
275
+ source: <20240211183923.131278-1-karthik.188@gmail.com>
276
+
277
+
278
+* kh/column-reject-negative-padding (2024-02-13) 2 commits
279
+ - column: guard against negative padding
280
+ - column: disallow negative padding
281
+
282
+ "git column" has been taught to reject negative padding value, as
283
+ it would lead to nonsense behaviour including division by zero.
284
+
285
+ Will merge to 'next'?
286
+ source: <cover.1707839454.git.code@khaugsbakk.name>
287
+
288
+--------------------------------------------------
289
+[Cooking]
290
291
* vn/rebase-with-cherry-pick-authorship (2024-02-08) 1 commit
151
- - sequencer: unset GIT_CHERRY_PICK_HELP for 'exec' commands
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
156
- Will merge to 'next'?
298
+ Will merge to 'master'.
299
source: <0adb1068-ef10-44ed-ad1d-e0927a09245d@gmail.com>
300
301
160
-* jc/no-lazy-fetch (2024-02-08) 1 commit
302
+* jc/no-lazy-fetch (2024-02-13) 1 commit
303
- git: --no-lazy-fetch option
304
305
"git --no-lazy-fetch cmd" allows to run "cmd" while disabling lazy
306
fetching of objects from the promisor remote, which may be handy
307
for debugging.
308
167
- Needs review.
309
+ Will merge to 'next'.
310
source: <xmqq1q9mmtpw.fsf@gitster.g>
311
312
@@ -174,23 +316,19 @@ Release tarballs are available at:
316
Adjust use of "rev-list --missing" in an existing tests so that it
317
does not depend on a buggy failure mode.
318
177
- Needs review.
319
+ Will merge to 'next'.
320
source: <xmqq7cjemttr.fsf@gitster.g>
321
180
---------------------------------------------------
181
-[Cooking]
322
183
-* gt/at-is-synonym-for-head-in-add-patch (2024-02-03) 3 commits
184
- - SQUASH???
323
+* 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'
186
- - add-patch: remove unnecessary NEEDSWORK comment
326
327
Teach "git checkout -p" and friends that "@" is a synonym for
328
"HEAD".
329
191
- Expecting a reroll.
192
- cf. <xmqqil31dqx6.fsf@gitster.g>
193
- source: <20240202150434.11256-1-shyamthakkar001@gmail.com>
330
+ Will merge to 'next'?
331
+ source: <20240211202035.7196-2-shyamthakkar001@gmail.com>
332
333
334
* js/unit-test-suite-runner (2024-02-03) 7 commits
@@ -210,62 +348,15 @@ Release tarballs are available at:
348
source: <cover.1706921262.git.steadmon@google.com>
349
350
213
-* jc/sign-buffer-failure-propagation-fix (2024-02-07) 2 commits
214
- (merged to 'next' on 2024-02-08 at badb96b5ac)
215
- + ssh signing: signal an error with a negative return value
216
- (merged to 'next' on 2024-02-07 at 2cedac9d38)
217
- + tag: fix sign_buffer() call to create a signed tag
218
-
219
- A failed "git tag -s" did not necessarily result in an error
220
- depending on the crypto backend, which has been corrected.
221
-
222
- Will merge to 'master'.
223
- source: <xmqq4jek9ko1.fsf@gitster.g>
224
- source: <xmqq5xyzr6tm.fsf@gitster.g>
225
-
226
-
351
* js/check-null-from-read-object-file (2024-02-06) 1 commit
228
- - Always check the return value of `repo_read_object_file()`
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
233
- Waiting for review responses.
234
- cf. <CAO_smVhrMn=-uF1B6+RA8A+VLCEN=o57zbQPtr8hpxRKY=qJRQ@mail.gmail.com>
235
- source: <pull.1650.git.1707143753726.gitgitgadget@gmail.com>
236
-
237
-
238
-* pb/template-for-single-commit-pr (2024-02-06) 1 commit
239
- (merged to 'next' on 2024-02-07 at 2a56c8eb13)
240
- + .github/PULL_REQUEST_TEMPLATE.md: add a note about single-commit PRs
241
-
242
- Doc update.
243
-
244
- Will merge to 'master'.
245
- source: <pull.1665.v2.git.git.1707225612576.gitgitgadget@gmail.com>
246
-
247
-
248
-* ps/report-failure-from-git-stash (2024-02-06) 1 commit
249
- (merged to 'next' on 2024-02-07 at a8a3f91f61)
250
- + builtin/stash: report failure to write to index
251
-
252
- "git stash" sometimes was silent even when it failed due to
253
- unwritable index file, which has been corrected.
254
-
358
Will merge to 'master'.
256
- source: <cb098cf88cbfcbf7c4872f8887856629b909cb91.1707197653.git.ps@pks.im>
257
-
258
-
259
-* tb/multi-pack-reuse-experiment (2024-02-05) 2 commits
260
- (merged to 'next' on 2024-02-08 at e92afaa170)
261
- + pack-objects: enable multi-pack reuse via `feature.experimental`
262
- + t5332-multi-pack-reuse.sh: extract pack-objects helper functions
263
-
264
- Setting `feature.experimental` opts the user into multi-pack reuse
265
- experiment
266
-
267
- Will merge to 'master'.
268
- source: <cover.1707173415.git.me@ttaylorr.com>
359
+ source: <pull.1650.git.1707143753726.gitgitgadget@gmail.com>
360
361
362
* ps/reftable-backend (2024-02-07) 3 commits
@@ -274,6 +365,7 @@ Release tarballs are available at:
365
(merged to 'next' on 2024-02-07 at 1115200acb)
366
+ ci: add jobs to test with the reftable backend
367
+ refs: introduce reftable backend
368
+ (this branch is used by kn/for-all-refs.)
369
370
Integrate the reftable code into the refs framework as a backend.
371
@@ -296,39 +388,21 @@ Release tarballs are available at:
388
source: <20240208135055.2705260-1-christian.couder@gmail.com>
389
390
299
-* ps/reftable-iteration-perf (2024-02-01) 7 commits
300
- - reftable/reader: add comments to `table_iter_next()`
301
- - reftable/record: don't try to reallocate ref record name
302
- - reftable/block: swap buffers instead of copying
303
- - reftable/pq: allocation-less comparison of entry keys
304
- - reftable/merged: skip comparison for records of the same subiter
305
- - reftable/merged: allocation-less dropping of shadowed records
306
- - reftable/record: introduce function to compare records by key
391
+* ps/reftable-iteration-perf (2024-02-12) 7 commits
392
+ (merged to 'next' on 2024-02-12 at 6abaf58383)
393
+ + reftable/reader: add comments to `table_iter_next()`
394
+ + reftable/record: don't try to reallocate ref record name
395
+ + reftable/block: swap buffers instead of copying
396
+ + reftable/pq: allocation-less comparison of entry keys
397
+ + reftable/merged: skip comparison for records of the same subiter
398
+ + reftable/merged: allocation-less dropping of shadowed records
399
+ + reftable/record: introduce function to compare records by key
400
401
The code to iterate over refs with the reftable backend has seen
402
some optimization.
403
311
- Expecting a reroll.
312
- cf. <Zbx6aDzXpYy4Is2t@tanuki>
313
- source: <cover.1706782841.git.ps@pks.im>
314
-
315
-
316
-* ps/reftable-styles (2024-02-06) 9 commits
317
- (merged to 'next' on 2024-02-07 at 18670512e2)
318
- + reftable/record: improve semantics when initializing records
319
- + reftable/merged: refactor initialization of iterators
320
- + reftable/merged: refactor seeking of records
321
- + reftable/stack: use `size_t` to track stack length
322
- + reftable/stack: use `size_t` to track stack slices during compaction
323
- + reftable/stack: index segments with `size_t`
324
- + reftable/stack: fix parameter validation when compacting range
325
- + reftable: introduce macros to allocate arrays
326
- + reftable: introduce macros to grow arrays
327
-
328
- Code clean-up in various reftable code paths.
329
-
330
- Will merge to 'master'.
331
- source: <cover.1707200355.git.ps@pks.im>
404
+ Will cook in 'next'.
405
+ source: <cover.1707726654.git.ps@pks.im>
406
407
408
* jc/github-actions-update (2024-02-02) 3 commits
@@ -336,6 +410,7 @@ Release tarballs are available at:
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
@@ -364,19 +439,19 @@ Release tarballs are available at:
439
source: <pull.1651.v2.git.1707324461.gitgitgadget@gmail.com>
440
441
367
-* pb/complete-config (2024-01-29) 5 commits
368
- - completion: add an use _ _git_compute_second_level_config_vars_for_section
369
- - builtin/help: add --config-all-for-completion
370
- - completion: add and use _ _git_compute_first_level_config_vars_for_section
371
- - completion: complete 'submodule.*' config variables
372
- - completion: add space after config variable names also in Bash 3
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
377
- Needs review.
378
- cf. <xmqq8r3w53nc.fsf@gitster.g>
379
- source: <pull.1660.v2.git.git.1706534881.gitgitgadget@gmail.com>
452
+ Will merge to 'master'.
453
+ cf. <Zcs34kGTqTbIana6@tanuki>
454
+ source: <pull.1660.v3.git.git.1707589943.gitgitgadget@gmail.com>
455
456
457
* rj/complete-reflog (2024-01-26) 4 commits
@@ -392,48 +467,17 @@ Release tarballs are available at:
467
source: <98daf977-dbad-4d3b-a293-6a769895088f@gmail.com>
468
469
395
-* ps/reftable-multi-level-indices-fix (2024-02-01) 6 commits
396
- (merged to 'next' on 2024-02-07 at 143f47a079)
397
- + reftable: document reading and writing indices
398
- + reftable/writer: fix writing multi-level indices
399
- + reftable/writer: simplify writing index records
400
- + reftable/writer: use correct type to iterate through index entries
401
- + reftable/reader: be more careful about errors in indexed seeks
402
- + Merge branch 'jc/reftable-core-fsync' into ps/reftable-multi-level-indices-fix
403
-
404
- Write multi-level indices for reftable has been corrected.
405
-
406
- Will merge to 'master'.
407
- source: <cover.1706773842.git.ps@pks.im>
408
-
409
-
410
-* ml/log-merge-with-cherry-pick-and-other-pseudo-heads (2024-02-08) 2 commits
411
- - revision: implement `git log --merge` also for rebase/cherry_pick/revert
470
+* ml/log-merge-with-cherry-pick-and-other-pseudo-heads (2024-02-12) 2 commits
471
+ - revision: implement `git log --merge` also for rebase/cherry-pick/revert
472
- revision: ensure MERGE_HEAD is a ref in prepare_show_merge
473
474
"git log --merge" learned to pay attention to CHERRY_PICK_HEAD and
475
other kinds of *_HEAD pseudorefs.
476
417
- Will merge to 'next'?
418
- source: <20240117081405.14012-1-mi.al.lohmann@gmail.com>
419
- source: <dfb582cf-b1e4-414d-bfe1-0f93d910ec54@kdbg.org>
420
-
421
-
422
-* bk/complete-bisect (2024-02-06) 7 commits
423
- (merged to 'next' on 2024-02-07 at ac95a595b7)
424
- + completion: bisect: recognize but do not complete view subcommand
425
- + completion: bisect: complete log opts for visualize subcommand
426
- + completion: new function __git_complete_log_opts
427
- + completion: bisect: complete missing --first-parent and - -no-checkout options
428
- + completion: bisect: complete custom terms and related options
429
- + completion: bisect: complete bad, new, old, and help subcommands
430
- + completion: tests: always use 'master' for default initial branch name
431
-
432
- Command line completion support (in contrib/) has been
433
- updated for "git bisect".
434
-
435
- Will merge to 'master'.
436
- source: <20240206215048.488344-1-britton.kerin@gmail.com>
477
+ Expecting a reroll.
478
+ cf. <790a3f11-5a8c-42f2-7a35-f2900c0299b4@gmail.com>
479
+ cf. <8384d1dc-b6c4-b853-9bf6-3d7ccee86d12@gmail.com>
480
+ source: <20240210-ml-log-merge-with-cherry-pick-and-other-pseudo-heads-v4-0-3bc9e62808f4@gmail.com>
481
482
483
* bk/complete-dirname-for-am-and-format-patch (2024-01-12) 1 commit
@@ -511,17 +555,6 @@ Release tarballs are available at:
555
source: <20231226233218.472054-1-gitster@pobox.com>
556
557
514
-* jc/bisect-doc (2024-02-07) 2 commits
515
- (merged to 'next' on 2024-02-07 at 914fa6775f)
516
- + bisect: document command line arguments for "bisect start"
517
- + bisect: document "terms" subcommand more fully
518
-
519
- Doc update.
520
-
521
- Will merge to 'master'.
522
- source: <20240207214436.538586-1-gitster@pobox.com>
523
-
524
-
558
* tb/path-filter-fix (2024-01-31) 16 commits
559
- bloom: introduce `deinit_bloom_filters()`
560
- commit-graph: reuse existing Bloom filters where possible
@@ -619,21 +652,6 @@ Release tarballs are available at:
652
source: <cover.1699569246.git.me@ttaylorr.com>
653
654
622
-* kn/for-all-refs (2024-01-29) 4 commits
623
- (merged to 'next' on 2024-01-30 at e7a9234a8b)
624
- + for-each-ref: avoid filtering on empty pattern
625
- + refs: introduce `refs_for_each_all_refs()`
626
- + refs: extract out `loose_fill_ref_dir_regular_file()`
627
- + refs: introduce `is_pseudoref()` and `is_headref()`
628
-
629
- "git for-each-ref" filters its output with prefixes given from the
630
- command line, but it did not honor an empty string to mean "pass
631
- everything", which has been corrected.
632
-
633
- Reverted out of 'next' to revamp its UI.
634
- source: <20240129113527.607022-1-karthik.188@gmail.com>
635
-
636
-
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