What's cooking (2023/08 #03)
Junio C Hamano committed
Aug 8, 2023 at 18:33 UTC
21dd98b20b0669b9b59690dac376a3b268dacb42
1 file changed
+235
-199
whats-cooking.txt
+235
-199
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Aug 2023, #02; Fri, 4)
3
-X-master-at: ac83bc5054c2ac489166072334b4147ce6d0fccb
4
-X-next-at: 6953b252045fa7a4c836b56ff7a46e3e85c8275b
2
+Subject: What's cooking in git.git (Aug 2023, #03; Tue, 8)
3
+X-master-at: a82fb66fed250e16d3010c75404503bea3f0ab61
4
+X-next-at: fd1ba4accffeede84a3a0c749bb6e1e407769a41
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Aug 2023, #02; Fri, 4)
7
+What's cooking in git.git (Aug 2023, #03; Tue, 8)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -17,8 +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.42-rc0 has been tagged. Hopefully people can help find and
21
-fix plenty of regressions before we tag -rc1 mid next week ;-)
20
+There are some last-minute fixes that update or add messages that
21
+are marked for i18n, and they may have to be fast-tracked to -rc1,
22
+which we may want to delay by one day for that reason.
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
@@ -51,168 +52,200 @@ Release tarballs are available at:
52
--------------------------------------------------
53
[Graduated to 'master']
54
54
-* hy/blame-in-bare-with-contents (2023-07-21) 1 commit
55
- (merged to 'next' on 2023-07-31 at 39ac96d8d8)
56
- + blame: allow --contents to work with bare repo
55
+* am/doc-sha256 (2023-07-31) 1 commit
56
+ (merged to 'next' on 2023-08-01 at d7419bf527)
57
+ + doc: sha256 is no longer experimental
58
+
59
+ Tone down the warning on SHA-256 repositories being an experimental
60
+ curiosity. We do not have support for them to interoperate with
61
+ traditional SHA-1 repositories, but at this point, we do not plan
62
+ to make breaking changes to SHA-256 repositories and there is no
63
+ longer need for such a strongly phrased warning.
64
+ source: <ZMe6KmzZGVubYpvO@adams>
65
58
- "git blame --contents=file" has been taught to work in a bare
59
- repository.
60
- source: <20230721035758.61956-1-hanyang.tony@bytedance.com>
66
67
+* ew/sha256-gcrypt-leak-fixes (2023-07-31) 3 commits
68
+ (merged to 'next' on 2023-08-01 at eed83801c3)
69
+ + sha256/gcrypt: die on gcry_md_open failures
70
+ + sha256/gcrypt: fix memory leak with SHA-256 repos
71
+ + sha256/gcrypt: fix build with SANITIZE=leak
72
63
-* ja/worktree-orphan-fix (2023-07-26) 3 commits
64
- (merged to 'next' on 2023-07-27 at e475016065)
65
- + t2400: rewrite regex to avoid unintentional PCRE
66
- + builtin/worktree.c: convert tab in advice to space
67
- + t2400: drop no-op `--sq` from rev-parse call
73
+ Leakfixes.
74
+ source: <20230731120808.1230210-1-e@80x24.org>
75
69
- Fix tests with unportable regex patterns.
70
- source: <20230726214202.15775-1-jacobabel@nullpo.dev>
76
77
+* rs/bundle-parseopt-cleanup (2023-07-31) 1 commit
78
+ (merged to 'next' on 2023-08-01 at 405eb138fa)
79
+ + bundle: use OPT_PASSTHRU_ARGV
80
73
-* jc/branch-in-use-error-message (2023-07-21) 1 commit
74
- (merged to 'next' on 2023-07-31 at 22f17d131b)
75
- + branch: update the message to refuse touching a branch in-use
81
+ Code clean-up.
82
+ source: <2dcb915f-b926-e024-6394-23aff200955c@web.de>
83
77
- "git branch -f X" to repoint the branch X said that X was "checked
78
- out" in another worktree, even when branch X was not and instead
79
- being bisected or rebased. The message was reworded to say the
80
- branch was "in use".
81
- source: <xmqqr0p1szhz.fsf_-_@gitster.g>
84
85
+* tb/commit-graph-tests (2023-07-24) 5 commits
86
+ (merged to 'next' on 2023-07-31 at 740a260315)
87
+ + t/lib-commit-graph.sh: avoid sub-shell in `graph_git_behavior()`
88
+ + t5328: avoid top-level directory changes
89
+ + t5318: avoid top-level directory changes
90
+ + t/lib-commit-graph.sh: avoid directory change in `graph_git_behavior()`
91
+ + t/lib-commit-graph.sh: allow `graph_read_expect()` in sub-directories
92
84
-* jc/doc-sent-patch-now-what (2023-07-27) 1 commit
85
- (merged to 'next' on 2023-07-31 at 51f5d9d465)
86
- + MyFirstContribution: refrain from self-iterating too much
93
+ Test updates.
94
+ source: <cover.1690216758.git.me@ttaylorr.com>
95
88
- Process document update.
89
- source: <xmqqmszg987u.fsf_-_@gitster.g>
96
+--------------------------------------------------
97
+[New Topics]
98
99
+* la/trailer-cleanups (2023-08-06) 5 commits
100
+ - trailer: rename *_DEFAULT enums to *_UNSPECIFIED
101
+ - trailer: teach find_patch_start about --no-divider
102
+ - trailer: split process_command_line_args into separate functions
103
+ - trailer: split process_input_file into separate pieces
104
+ - trailer: separate public from internal portion of trailer_iterator
105
92
-* jc/parse-options-short-help (2023-07-19) 3 commits
93
- (merged to 'next' on 2023-07-31 at e076d1f497)
94
- + short help: allow a gap smaller than USAGE_GAP
95
- + remote: simplify "remote add --tags" help text
96
- + short help: allow multi-line opthelp
106
+ Code clean-up.
107
98
- Command line parser fix, and a small parse-options API update.
99
- source: <xmqq5y6gg8fn.fsf@gitster.g>
108
+ Needs review.
109
+ source: <pull.1563.git.1691211879.gitgitgadget@gmail.com>
110
111
102
-* jc/retire-get-sha1-hex (2023-07-24) 1 commit
103
- (merged to 'next' on 2023-07-27 at eeb9cc37f5)
104
- + hex: retire get_sha1_hex()
112
+* la/trailer-test-and-doc-updates (2023-08-06) 5 commits
113
+ - trailer --no-divider help: describe usual "---" meaning
114
+ - trailer: trailer location is a place, not an action
115
+ - trailer: add tests to check defaulting behavior with --no-* flags
116
+ - trailer test description: this tests --where=after, not --where=before
117
+ - trailer tests: make test cases self-contained
118
106
- The implementation of "get_sha1_hex()" that reads a hexadecimal
107
- string that spells a full object name has been extended to cope
108
- with any hash function used in the repository, but the "sha1" in
109
- its name survived. Rename it to get_hash_hex(), a name that is
110
- more consistent within its friends like get_hash_hex_algop().
111
- source: <xmqq1qgwoqgo.fsf_-_@gitster.g>
119
+ Test coverage improvement for trailers.
120
121
+ Needs review.
122
+ source: <pull.1564.git.1691210737.gitgitgadget@gmail.com>
123
114
-* la/doc-choose-starting-point (2023-07-14) 5 commits
115
- (merged to 'next' on 2023-07-19 at 5a807cae46)
116
- + SubmittingPatches: simplify guidance for choosing a starting point
117
- + SubmittingPatches: emphasize need to communicate non-default starting points
118
- + SubmittingPatches: de-emphasize branches as starting points
119
- + SubmittingPatches: discuss subsystems separately from git.git
120
- + SubmittingPatches: reword awkward phrasing
121
- (this branch is used by la/doc-choose-starting-point-fixup.)
124
123
- Clarify how to choose the starting point for a new topic in
124
- developer guidance document.
125
+* jk/repack-leakfix (2023-08-08) 1 commit
126
+ - repack: free geometry struct
127
126
- Will merge to 'master' together with the follow-on topic.
127
- source: <pull.1556.v2.git.1689314493.gitgitgadget@gmail.com>
128
+ Leakfix.
129
130
+ Will merge to 'next'.
131
+ source: <20230808185023.GA3498623@coredump.intra.peff.net>
132
130
-* la/doc-choose-starting-point-fixup (2023-07-27) 3 commits
131
- (merged to 'next' on 2023-07-28 at 047dcae31c)
132
- + SubmittingPatches: use of older maintenance tracks is an exception
133
- + SubmittingPatches: explain why 'next' and above are inappropriate base
134
- + SubmittingPatches: choice of base for fixing an older maintenance track
135
- (this branch uses la/doc-choose-starting-point.)
133
137
- Clarify how to pick a starting point for a new topic in the
138
- SubmittingPatches document.
134
+* jk/send-email-with-new-readline (2023-08-08) 2 commits
135
+ - send-email: avoid creating more than one Term::ReadLine object
136
+ - send-email: drop FakeTerm hack
137
140
- Will merge to 'master', together with the underlying topic.
141
- source: <pull.1556.v2.git.1689314493.gitgitgadget@gmail.com>
142
- source: <pull.1556.v3.git.1690340701.gitgitgadget@gmail.com>
138
+ Adjust to newer Term::ReadLine to prevent it from breaking
139
+ the interactive prompt code in send-email.
140
141
+ Will merge to 'next'.
142
+ source: <20230808180935.GA2096901@coredump.intra.peff.net>
143
145
-* pv/doc-submodule-update-settings (2023-07-25) 1 commit
146
- (merged to 'next' on 2023-07-27 at e27b5b7ba8)
147
- + doc: highlight that .gitmodules does not support !command
144
149
- Rewrite the description of giving a custom command to the
150
- submodule.<name>.update configuration variable.
151
- source: <20230725212218.711116-1-pvutov@imap.cc>
145
+* js/allow-t4000-to-be-indented-with-spaces (2023-08-08) 1 commit
146
+ - t0040: declare non-tab indentation to be okay in this script
147
153
---------------------------------------------------
154
-[New Topics]
148
+ File attribute update.
149
156
-* jc/rerere-cleanup (2023-08-03) 5 commits
157
- - rerere: plug small strbuf leak
158
- - rerere: modernize use of empty strbuf
159
- - rerere: try_merge() should use LL_MERGE_ERROR when it means an error
160
- - rerere: fix comment on handle_file() helper
161
- - rerere: simplify check_one_conflict() helper function
162
- (this branch uses jc/unresolve-removal.)
150
+ Will merge to 'next'.
151
+ source: <pull.1568.git.1691491054706.gitgitgadget@gmail.com>
152
164
- Code clean-up.
153
166
- Not ready to be reviewed yet.
167
- source: <20230731224409.4181277-1-gitster@pobox.com>
154
+* ob/rebase-conflict-advice-i18n-fix (2023-08-07) 1 commit
155
+ - advice: handle "rebase" in error_resolve_conflict()
156
157
+ i18n coverage improvement and avoidance of sentence lego.
158
170
-* ma/locate-in-path-for-windows (2023-08-04) 3 commits
171
- - docs: update when `git bisect visualize` uses `gitk`
172
- - compat/mingw: implement a native locate_in_PATH()
173
- - run-command: conditionally define locate_in_PATH()
159
+ Will merge to 'next'.
160
+ source: <20230807170935.2336715-1-oswald.buddenhagen@gmx.de>
161
175
- "git bisect visualize" stopped running "gitk" on Git for Windows
176
- when the command was reimplemented in C around Git 2.34 timeframe.
177
- This has been corrected.
162
+
163
+* rs/parse-opt-forbid-set-int-0-without-noneg (2023-08-08) 1 commit
164
+ - parse-options: disallow negating OPTION_SET_INT 0
165
+
166
+ Developer support to detect meaningless combination of options.
167
168
Will merge to 'next'.
180
- source: <pull.1560.v2.git.1691122124.gitgitgadget@gmail.com>
169
+ source: <c4cd1591-3a83-920a-6a80-19ffbfe3089d@web.de>
170
171
183
-* pw/rebase-skip-commit-message-fix (2023-08-03) 1 commit
184
- - rebase --skip: fix commit message clean up when skipping squash
172
+* ds/maintenance-schedule-fuzz (2023-08-07) 6 commits
173
+ - maintenance: use random minute in systemd scheduler
174
+ - maintenance: swap method locations
175
+ - maintenance: use random minute in cron scheduler
176
+ - maintenance: use random minute in Windows scheduler
177
+ - maintenance: use random minute in launchctl scheduler
178
+ - maintenance: add get_random_minute()
179
+
180
+ Allow "git maintenance" schedule to be randomly distributed.
181
+
182
+ Still under discussion.
183
+ Expecting a reroll.
184
+ source: <pull.1567.git.1691434300.gitgitgadget@gmail.com>
185
+
186
+
187
+* ob/send-email-interactive-failure (2023-08-07) 1 commit
188
+ - send-email: prompt-dependent exit codes
189
+
190
+ "git send-email" exits with non-zero status when end-user
191
+ interaction causes any prepared message not to be sent.
192
+
193
+ Expecting a reroll.
194
+ Without an opt-in fix, this will be a backward-incompatible
195
+ change that needs mention in the release notes.
196
+ source: <20230807165850.2335067-1-oswald.buddenhagen@gmx.de>
197
+
198
+
199
+* ob/sequencer-empty-hint-fix (2023-08-07) 1 commit
200
+ - sequencer: rectify empty hint in call of require_clean_work_tree()
201
+
202
+ Under some unspecified condition, a code that calls into the
203
+ sequencer can produce an extra "error:" output that has no
204
+ meaningful message on it.
205
+
206
+ Expecting a reroll.
207
+ cf. <xmqqcyzx6ma1.fsf@gitster.g>
208
+ source: <20230807170935.2336730-1-oswald.buddenhagen@gmx.de>
209
186
- "git rebase -i" with a series of squash/fixup, when one of the
187
- steps stopped in conflicts and ended up getting skipped, did not
188
- handle the accumulated commit log messages, which has been
189
- corrected.
210
+
211
+* ob/test-lib-rebase-fake-editor-updates (2023-08-07) 3 commits
212
+ - t/lib-rebase: improve documentation of set_fake_editor()
213
+ - t/lib-rebase: set_fake_editor(): handle FAKE_LINES more consistently
214
+ - t/lib-rebase: set_fake_editor(): fix recognition of reset's short command
215
+
216
+ Test updates.
217
218
Will merge to 'next'.
192
- source: <pull.1558.git.git.1691068176051.gitgitgadget@gmail.com>
219
+ source: <20230807170935.2336663-1-oswald.buddenhagen@gmx.de>
220
221
195
-* bc/ignore-cland-cache (2023-08-04) 1 commit
196
- (merged to 'next' on 2023-08-04 at 5cf8d41911)
197
- + gitignore: ignore clangd .cache directory
222
+* rj/branch-in-use-error-message (2023-08-08) 2 commits
223
+ - branch: error message checking out a branch in use
224
+ - branch: error message deleting a branch in use
225
199
- .gitignore update.
226
+ A message written in olden time prevented a branch from getting
227
+ checked out saying it is already checked out elsewhere, but these
228
+ days, we treat a branch that is being bisected or rebased just like
229
+ a branch that is checked out and protect it. Rephrase the message
230
+ to say that the branch is in use.
231
201
- Will merge to 'master'.
202
- source: <20230804171328.1737188-1-sandals@crustytoothpaste.net>
232
+ Will merge to 'next'.
233
+ source: <7710c002-0832-d8f6-59b8-30119bd5efe6@gmail.com>
234
235
--------------------------------------------------
236
[Stalled]
237
207
-* mh/credential-libsecret-attrs (2023-06-16) 1 commit
208
- - credential/libsecret: store new attributes
238
+* sl/sparse-check-attr (2023-07-18) 3 commits
239
+ - check-attr: integrate with sparse-index
240
+ - attr.c: read attributes in a sparse directory
241
+ - t1092: add tests for 'git check-attr'
242
210
- The way authentication related data other than passwords (e.g.
211
- oath token and password expiration data) are stored in libsecret
212
- keyrings has been rethought.
243
+ Teach "git check-attr" work better with sparse-index.
244
214
- Needs review.
215
- source: <pull.1469.v5.git.git.1686945306242.gitgitgadget@gmail.com>
245
+ Expecting a reroll.
246
+ cf. <c3ebe3b4-88b9-8ca2-2ee3-39a3e0d82201@github.com>
247
+ cf. <5e478d8b-9ef4-864b-41e4-e0a79877d278@github.com>
248
+ source: <20230718232916.31660-1-cheskaqiqi@gmail.com>
249
250
251
* cc/git-replay (2023-06-03) 15 commits
@@ -264,6 +297,70 @@ Release tarballs are available at:
297
--------------------------------------------------
298
[Cooking]
299
300
+* mh/credential-libsecret-attrs (2023-06-16) 1 commit
301
+ (merged to 'next' on 2023-08-08 at dc73a2c55a)
302
+ + credential/libsecret: store new attributes
303
+
304
+ The way authentication related data other than passwords (e.g.
305
+ oath token and password expiration data) are stored in libsecret
306
+ keyrings has been rethought.
307
+
308
+ Will cook in 'next'.
309
+ Needs review.
310
+ source: <pull.1469.v5.git.git.1686945306242.gitgitgadget@gmail.com>
311
+
312
+
313
+* jc/rerere-cleanup (2023-08-03) 5 commits
314
+ - rerere: plug small strbuf leak
315
+ - rerere: modernize use of empty strbuf
316
+ - rerere: try_merge() should use LL_MERGE_ERROR when it means an error
317
+ - rerere: fix comment on handle_file() helper
318
+ - rerere: simplify check_one_conflict() helper function
319
+ (this branch uses jc/unresolve-removal.)
320
+
321
+ Code clean-up.
322
+
323
+ Not ready to be reviewed yet.
324
+ source: <20230731224409.4181277-1-gitster@pobox.com>
325
+
326
+
327
+* ma/locate-in-path-for-windows (2023-08-04) 3 commits
328
+ (merged to 'next' on 2023-08-06 at 02bc13f4a3)
329
+ + docs: update when `git bisect visualize` uses `gitk`
330
+ + compat/mingw: implement a native locate_in_PATH()
331
+ + run-command: conditionally define locate_in_PATH()
332
+
333
+ "git bisect visualize" stopped running "gitk" on Git for Windows
334
+ when the command was reimplemented in C around Git 2.34 timeframe.
335
+ This has been corrected.
336
+
337
+ Will merge to 'master'.
338
+ source: <pull.1560.v2.git.1691122124.gitgitgadget@gmail.com>
339
+
340
+
341
+* pw/rebase-skip-commit-message-fix (2023-08-03) 1 commit
342
+ (merged to 'next' on 2023-08-06 at 1e44443e65)
343
+ + rebase --skip: fix commit message clean up when skipping squash
344
+
345
+ "git rebase -i" with a series of squash/fixup, when one of the
346
+ steps stopped in conflicts and ended up getting skipped, did not
347
+ handle the accumulated commit log messages, which has been
348
+ corrected.
349
+
350
+ Will merge to 'master'.
351
+ source: <pull.1558.git.git.1691068176051.gitgitgadget@gmail.com>
352
+
353
+
354
+* bc/ignore-clangd-cache (2023-08-04) 1 commit
355
+ (merged to 'next' on 2023-08-04 at 5cf8d41911)
356
+ + gitignore: ignore clangd .cache directory
357
+
358
+ .gitignore update.
359
+
360
+ Will merge to 'master'.
361
+ source: <20230804171328.1737188-1-sandals@crustytoothpaste.net>
362
+
363
+
364
* pw/rebase-i-after-failure (2023-08-01) 7 commits
365
- rebase -i: fix adding failed command to the todo list
366
- rebase --continue: refuse to commit after failed command
@@ -334,43 +431,10 @@ Release tarballs are available at:
431
source: <48745298-f12b-8efb-4e48-90d2c22a8349@gmail.com>
432
433
337
-* ew/sha256-gcrypt-leak-fixes (2023-07-31) 3 commits
338
- (merged to 'next' on 2023-08-01 at eed83801c3)
339
- + sha256/gcrypt: die on gcry_md_open failures
340
- + sha256/gcrypt: fix memory leak with SHA-256 repos
341
- + sha256/gcrypt: fix build with SANITIZE=leak
342
-
343
- Leakfixes.
344
-
345
- Will merge to 'master'.
346
- source: <20230731120808.1230210-1-e@80x24.org>
347
-
348
-
349
-* rs/bundle-parseopt-cleanup (2023-07-31) 1 commit
350
- (merged to 'next' on 2023-08-01 at 405eb138fa)
351
- + bundle: use OPT_PASSTHRU_ARGV
352
-
353
- Code clean-up.
354
-
355
- Will merge to 'master'.
356
- source: <2dcb915f-b926-e024-6394-23aff200955c@web.de>
357
-
358
-
359
-* am/doc-sha256 (2023-07-31) 1 commit
360
- (merged to 'next' on 2023-08-01 at d7419bf527)
361
- + doc: sha256 is no longer experimental
362
-
363
- Tone down the warning on SHA-256 repositories being an experimental
364
- curiosity. We do not have support for them to interoperate with
365
- traditional SHA-1 repositories, but at this point, we do not plan
366
- to make breaking changes to SHA-256 repositories and there is no
367
- longer need for such a strongly phrased warning.
368
-
369
- Will merge to 'master'.
370
- source: <ZMe6KmzZGVubYpvO@adams>
371
-
372
-
373
-* rs/parse-options-negation-help (2023-07-24) 5 commits
434
+* rs/parse-options-negation-help (2023-08-06) 8 commits
435
+ - parse-options: simplify usage_padding()
436
+ - parse-options: no --[no-]no-...
437
+ - parse-options: factor out usage_indent() and usage_padding()
438
- parse-options: show negatability of options in short help
439
- t1502: test option negation
440
- t1502: move optionspec help output to a file
@@ -380,54 +444,25 @@ Release tarballs are available at:
444
"git cmd -h" learned to signal which options can be negated by
445
listing such options like "--[no-]opt".
446
383
- Will merge to 'next'.
384
- I personally liked a later suggestion to deal with "--[no-]no-foo"
385
- but that can be done as a separate enhancement.
386
- cf. <31b71333-de8b-d9a8-3ec4-1bad9cae2bf3@web.de>
387
- cf. <xmqqjzug14jo.fsf@gitster.g>
388
- source: <4d01e971-07cb-4f11-3cc6-9d9f21e590c1@web.de>
389
-
390
-
391
-* tb/commit-graph-tests (2023-07-24) 5 commits
392
- (merged to 'next' on 2023-07-31 at 740a260315)
393
- + t/lib-commit-graph.sh: avoid sub-shell in `graph_git_behavior()`
394
- + t5328: avoid top-level directory changes
395
- + t5318: avoid top-level directory changes
396
- + t/lib-commit-graph.sh: avoid directory change in `graph_git_behavior()`
397
- + t/lib-commit-graph.sh: allow `graph_read_expect()` in sub-directories
398
-
399
- Test updates.
400
-
401
- Will merge to 'master'.
402
- source: <cover.1690216758.git.me@ttaylorr.com>
403
-
404
-
405
-* sl/sparse-check-attr (2023-07-18) 3 commits
406
- - check-attr: integrate with sparse-index
407
- - attr.c: read attributes in a sparse directory
408
- - t1092: add tests for 'git check-attr'
409
-
410
- Teach "git check-attr" work better with sparse-index.
411
-
412
- Expecting a reroll.
413
- cf. <c3ebe3b4-88b9-8ca2-2ee3-39a3e0d82201@github.com>
414
- cf. <5e478d8b-9ef4-864b-41e4-e0a79877d278@github.com>
415
- source: <20230718232916.31660-1-cheskaqiqi@gmail.com>
447
+ Comments?
448
+ source: <e4d46d97-1cd4-7fea-afd1-7de5023b1b09@web.de>
449
450
451
* mh/credential-erase-improvements-more (2023-07-26) 2 commits
419
- - credential/wincred: erase matching creds only
420
- - credential/libsecret: erase matching creds only
452
+ (merged to 'next' on 2023-08-08 at fd1ba4accf)
453
+ + credential/wincred: erase matching creds only
454
+ + credential/libsecret: erase matching creds only
455
456
Update two credential helpers to correctly match which credential
457
to erase; they dropped not the ones with stale password.
458
459
+ Will cook in 'next'.
460
Needs review.
461
source: <pull.1527.v2.git.git.1690387585634.gitgitgadget@gmail.com>
462
source: <pull.1529.git.git.1687596777147.gitgitgadget@gmail.com>
463
464
430
-* cc/repack-sift-filtered-objects-to-separate-pack (2023-07-24) 8 commits
465
+* cc/repack-sift-filtered-objects-to-separate-pack (2023-08-08) 8 commits
466
. gc: add `gc.repackFilterTo` config option
467
. repack: implement `--filter-to` for storing filtered out objects
468
. gc: add `gc.repackFilter` config option
@@ -440,21 +475,21 @@ Release tarballs are available at:
475
"git repack" machinery learns to pay attention to the "--filter="
476
option.
477
443
- Breaks CI with some environment variables configured.
444
- cf. <xmqqo7jzh9mh.fsf@gitster.g>
445
- source: <20230724085909.3831831-1-christian.couder@gmail.com>
478
+ Comments?
479
+ source: <20230808082608.582319-1-christian.couder@gmail.com>
480
481
448
-* js/doc-unit-tests (2023-06-30) 1 commit
449
- - unit tests: Add a project plan document
482
+* js/doc-unit-tests (2023-08-07) 1 commit
483
+ - unit tests: add a project plan document
484
485
Process to add some form of low-level unit tests has started.
486
453
- Still filling in blanks.
454
- source: <0169ce6fb9ccafc089b74ae406db0d1a8ff8ac65.1688165272.git.steadmon@google.com>
487
+ Comments?
488
+ source: <c7dca1a805a16fd4fd68e86efeec97510e3ac4b8.1691449216.git.steadmon@google.com>
489
490
457
-* jt/path-filter-fix (2023-08-01) 7 commits
491
+* jt/path-filter-fix (2023-08-08) 8 commits
492
+ - commit-graph: fix small leak with invalid changedPathsVersion
493
(merged to 'next' on 2023-08-03 at d99958c287)
494
+ commit-graph: new filter ver. that fixes murmur3
495
+ repo-settings: introduce commitgraph.changedPathsVersion
@@ -468,6 +503,7 @@ Release tarballs are available at:
503
on systems whose "char" is unsigned; update the implementation and
504
bump the format version to 2.
505
471
- Will merge to 'master'.
506
+ Will cook in 'next'.
507
cf. <ZMqp6K2iXixWH/zT@nand.local>
508
source: <cover.1690912539.git.jonathantanmy@google.com>
509
+ source: <20230808192240.GA4091261@coredump.intra.peff.net>