What's cooking (2024/07 #09)
Junio C Hamano committed
Jul 29, 2024 at 09:50 UTC
45c2780f9ef8149ca1b0e2ed3c9bd15a872f35eb
1 file changed
+161
-82
whats-cooking.txt
+161
-82
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Jul 2024, #08; Wed, 24)
3
-X-master-at: ad57f148c6b5f8735b62238dda8f571c582e0e54
4
-X-next-at: 509ed76dc8ffb8c65e563e151ada58240c08e9db
2
+Subject: What's cooking in git.git (Jul 2024, #09; Mon, 29)
3
+X-master-at: 39bf06adf96da25b87c9aa7d35a32ef3683eb4a4
4
+X-next-at: 1c80b25241079052bdf3727e0ab9a5d77c51ea6e
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Jul 2024, #08; Wed, 24)
7
+What's cooking in git.git (Jul 2024, #09; Mon, 29)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -17,11 +17,16 @@ 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.46-rc2 has been tagged. From now on until the final release,
21
-which is planned to happen near the end of this month, please make
22
-sure you place priorities on finding and fixing new regressions
23
-introduced during this cycle over finding and fixing old bugs, over
24
-any shiny new features.
20
+Git 2.46 has been tagged. As usual, we'll wait for embarrassing
21
+bugs to be reported for a week or so, try to fix them, and then
22
+reopen the tree for the next iteration (probably called 2.47).
23
+
24
+We already have known fallouts left from the removal of fallback to
25
+SHA-1 in operations that do not require an repository, which we may
26
+want to address next. There may be more work needed to alleviate
27
+the issues caused by the over-eager defense-in-depth changes
28
+introduced by 2.45.1, even though they were somewhat loosened in
29
+2.45.2 already.
30
31
Copies of the source code to Git live in many repositories, and the
32
following is a list of the ones I push into or their mirrors. Some
@@ -52,67 +57,120 @@ Release tarballs are available at:
57
https://www.kernel.org/pub/software/scm/git/
58
59
--------------------------------------------------
55
-[Graduated to 'master']
60
+[New Topics]
61
57
-* ds/midx-write-repack-fix (2024-07-19) 2 commits
58
- (merged to 'next' on 2024-07-22 at 0a64b3ed42)
59
- + midx-write: revert use of --stdin-packs
60
- + t5319: add failing test case for repack/expire
62
+* ja/doc-synopsis-markup (2024-07-24) 3 commits
63
+ - doc: apply synopsis simplification on git-clone and git-init
64
+ - doc: update the guidelines to reflect the current formatting rules
65
+ - doc: introduce a synopsis custom paragraph attribute
66
62
- Repacking a repository with multi-pack index started making stupid
63
- pack selections in Git 2.45, which has been corrected.
64
- source: <pull.1764.git.1721332546.gitgitgadget@gmail.com>
67
+ The way AsciiDoc is used for SYNOPSIS part of the manual pages has
68
+ been revamped. The sources, at least for the simple cases, got
69
+ vastly pleasant to work with.
70
71
+ Inviting further discussion.
72
+ source: <pull.1766.v2.git.1721855179.gitgitgadget@gmail.com>
73
67
-* ja/doc-markup-updates-fix (2024-07-20) 1 commit
68
- (merged to 'next' on 2024-07-23 at eedc41259a)
69
- + doc: git-clone fix discrepancy between asciidoc and asciidoctor
74
71
- Fix documentation mark-up regression in 2.45.
72
- cf. <xmqqv80w0zrx.fsf@gitster.g>
73
- source: <pull.1765.git.1721496853517.gitgitgadget@gmail.com>
75
+* ps/doc-more-c-coding-guidelines (2024-07-24) 3 commits
76
+ - Documentation: document difference between release and free
77
+ - Documentation: document naming schema for struct-related functions
78
+ - Documentation: clarify indentation style for C preprocessor directives
79
80
+ Some project conventions have been added to CodingGuidelines.
81
76
-* js/doc-markup-updates-fix (2024-07-23) 2 commits
77
- (merged to 'next' on 2024-07-23 at 9a4fa8f9d0)
78
- + Doc: fix Asciidoctor css workaround
79
- + asciidoctor: fix `synopsis` rendering
82
+ Inviting further discussion.
83
+ source: <cover.1721818488.git.ps@pks.im>
84
81
- Work around asciidoctor's css that renders `monospace` material
82
- in the SYNOPSIS section of manual pages as block elements.
83
- cf. <xmqqv80w0zrx.fsf@gitster.g>
84
- source: <pull.1749.v2.git.git.1721679949618.gitgitgadget@gmail.com>
85
86
+* tc/fetch-bundle-uri (2024-07-24) 3 commits
87
+ - fetch: use bundle URIs when having creationToken heuristic
88
+ - transport: introduce transport_has_remote_bundle_uri()
89
+ - clone: remove double bundle list clear code
90
87
-* ps/ref-storage-migration-fix (2024-07-23) 1 commit
88
- (merged to 'next' on 2024-07-23 at ebf4e7c214)
89
- + refs: fix format migration on Cygwin
91
+ Allow "git fetch" take advantage of bundleURI feature.
92
91
- Hotfix for a topic already in -rc.
92
- source: <d031aef5552d894784650a8c6580925e877df794.1721731179.git.ps@pks.im>
93
+ Needs review.
94
+ source: <20240724144957.3033840-1-toon@iotcl.com>
95
94
---------------------------------------------------
95
-[New Topics]
96
97
-* ps/p4-tests-updates (2024-07-23) 3 commits
98
- - t98xx: mark Perforce tests as memory-leak free
99
- - ci: update Perforce version to r23.2
100
- - t98xx: fix Perforce tests with p4d r23 and newer
97
+* as/show-ref-option-help-update (2024-07-25) 1 commit
98
+ (merged to 'next' on 2024-07-26 at bbdc971c38)
99
+ + show-ref: improve short help messages of options
100
102
- Perforce tests have been updated.
101
+ A few descriptions in "git show-ref -h" have been clarified.
102
104
- Needs review.
105
- source: <cover.1721740612.git.ps@pks.im>
103
+ Will merge to 'master'.
104
+ source: <20240724111116.91615-1-ash@kambanaria.org>
105
106
108
-* jc/doc-one-shot-export-with-shell-func (2024-07-23) 1 commit
109
- (merged to 'next' on 2024-07-23 at 621c29e4f6)
110
- + CodingGuidelines: document a shell that "fails" "VAR=VAL shell_func"
107
+* jc/doc-rebase-fuzz-vs-offset-fix (2024-07-25) 1 commit
108
+ (merged to 'next' on 2024-07-26 at 6f784b0c1c)
109
+ + doc: difference in location to apply is "offset", not "fuzz"
110
112
- It has been documented that we avoid "VAR=VAL shell_func" and why.
111
+ "git rebase --help" referred to "offset" (the difference between
112
+ the location a change was taken from and the change gets replaced)
113
+ incorrectly and called it "fuzz", which has been corrected.
114
114
- Will cook in 'next'.
115
- source: <xmqqwmld55y1.fsf@gitster.g>
115
+ Will merge to 'master'.
116
+ source: <xmqqplr1fkla.fsf@gitster.g>
117
+
118
+
119
+* jc/doc-reviewing-guidelines-positive-reviews (2024-07-25) 1 commit
120
+ (merged to 'next' on 2024-07-26 at 8f878efb0d)
121
+ + ReviewingGuidelines: encourage positive reviews more
122
+
123
+ The reviewing guidelines document now explicitly encourages people
124
+ to give positive reviews and how.
125
+
126
+ Will merge to 'master'.
127
+ source: <xmqqle1pjwtt.fsf@gitster.g>
128
+
129
+
130
+* jc/leakfix-hashfile (2024-07-26) 1 commit
131
+ - csum-file: introduce discard_hashfile()
132
+
133
+ source: <xmqqle1p1367.fsf@gitster.g>
134
+
135
+
136
+* jc/leakfix-mailmap (2024-07-26) 1 commit
137
+ - mailmap: plug memory leak in read_mailmap_blob()
138
+
139
+ source: <xmqqcyn112xi.fsf@gitster.g>
140
+
141
+
142
+* jr/ls-files-expand-literal-doc (2024-07-26) 1 commit
143
+ - doc: fix hex code escapes in git-ls-files
144
+
145
+ source: <CACStHN-Gs2Sxej+md6zWr3V1dFo+pp=B4yEPm9=uPambDR2NaQ@mail.gmail.com>
146
+
147
+
148
+* ps/leakfixes-part-3 (2024-07-26) 23 commits
149
+ - commit-reach: fix trivial memory leak when computing reachability
150
+ - convert: fix leaking config strings
151
+ - entry: fix leaking pathnames during delayed checkout
152
+ - object-name: fix leaking commit list items
153
+ - t/test-repository: fix leaking repository
154
+ - builtin/credential-cache: fix trivial leaks
155
+ - builtin/worktree: fix leaking derived branch names
156
+ - builtin/shortlog: fix various trivial memory leaks
157
+ - builtin/rerere: fix various trivial memory leaks
158
+ - builtin/credential-store: fix leaking credential
159
+ - builtin/show-branch: fix several memory leaks
160
+ - builtin/rev-parse: fix memory leak with `--parseopt`
161
+ - builtin/stash: fix various trivial memory leaks
162
+ - builtin/remote: fix various trivial memory leaks
163
+ - builtin/remote: fix leaking strings in `branch_list`
164
+ - builtin/ls-remote: fix leaking `pattern` strings
165
+ - builtin/submodule--helper: fix various trivial memory leaks
166
+ - builtin/name-rev: fix various trivial memory leaks
167
+ - builtin/describe: fix trivial memory leak when describing blob
168
+ - builtin/describe: fix leaking array when running diff-index
169
+ - builtin/describe: fix memory leak with `--contains=`
170
+ - builtin/log: fix leaking branch name when creating cover letters
171
+ - builtin/replay: plug leaking `advance_name` variable
172
+
173
+ source: <cover.1721995576.git.ps@pks.im>
174
175
--------------------------------------------------
176
[Stalled]
@@ -204,6 +262,27 @@ Release tarballs are available at:
262
--------------------------------------------------
263
[Cooking]
264
265
+* ps/p4-tests-updates (2024-07-23) 3 commits
266
+ - t98xx: mark Perforce tests as memory-leak free
267
+ - ci: update Perforce version to r23.2
268
+ - t98xx: fix Perforce tests with p4d r23 and newer
269
+
270
+ Perforce tests have been updated.
271
+
272
+ Needs review.
273
+ source: <cover.1721740612.git.ps@pks.im>
274
+
275
+
276
+* jc/doc-one-shot-export-with-shell-func (2024-07-23) 1 commit
277
+ (merged to 'next' on 2024-07-23 at 621c29e4f6)
278
+ + CodingGuidelines: document a shell that "fails" "VAR=VAL shell_func"
279
+
280
+ It has been documented that we avoid "VAR=VAL shell_func" and why.
281
+
282
+ Will merge to 'master'.
283
+ source: <xmqqwmld55y1.fsf@gitster.g>
284
+
285
+
286
* ag/git-svn-global-ignores (2024-07-18) 2 commits
287
- git-svn: use `svn:global-ignores` to create .gitignore
288
- git-svn: add public property `svn:global-ignores`
@@ -216,27 +295,29 @@ Release tarballs are available at:
295
296
297
* jc/how-to-maintain-updates (2024-07-19) 2 commits
219
- - howto-maintain: update daily tasks
220
- - howto-maintain: cover a whole development cycle
298
+ (merged to 'next' on 2024-07-26 at c950efa46d)
299
+ + howto-maintain: update daily tasks
300
+ + howto-maintain: cover a whole development cycle
301
302
Doc update.
303
224
- Will merge to 'next'?
304
+ Will merge to 'master'.
305
source: <xmqq1q3phzpi.fsf@gitster.g>
306
307
228
-* es/shell-check-updates (2024-07-22) 4 commits
229
- - check-non-portable-shell: suggest alternative for `VAR=val shell-func`
308
+* es/shell-check-updates (2024-07-26) 5 commits
309
- check-non-portable-shell: improve `VAR=val shell-func` detection
310
+ - check-non-portable-shell: suggest alternative for `VAR=val shell-func`
311
+ - check-non-portable-shell: loosen one-shot assignment error message
312
- t4034: fix use of one-shot variable assignment with shell function
232
- - t3430: modernize one-shot "VAR=val shell-func" invocation
313
+ - t3430: drop unnecessary one-shot "VAR=val shell-func" invocation
314
315
Test script linter has been updated to catch an attempt to use
316
one-shot export construct "VAR=VAL func" for shell functions (which
317
does not work for some shells) better.
318
238
- Will merge to 'next'?
239
- source: <20240722065915.80760-1-ericsunshine@charter.net>
319
+ Will merge to 'next'.
320
+ source: <20240727053509.34339-1-ericsunshine@charter.net>
321
322
323
* jc/safe-directory (2024-07-22) 3 commits
@@ -260,7 +341,7 @@ Release tarballs are available at:
341
with an empty line (not a line with a single space on it), which
342
has been corrected.
343
263
- Will cook in 'next'.
344
+ Will merge to 'master'.
345
source: <pull.1763.v2.git.1721491320.gitgitgadget@gmail.com>
346
347
@@ -270,7 +351,7 @@ Release tarballs are available at:
351
352
Docfix.
353
273
- Will cook in 'next'.
354
+ Will merge to 'master'.
355
source: <20240722225302.124356-1-tomasn@posteo.net>
356
357
@@ -296,7 +377,7 @@ Release tarballs are available at:
377
A build tweak knob has been simplified by not setting the value
378
that is already the default; another unused one has been removed.
379
299
- Will cook in 'next'.
380
+ Will merge to 'master'.
381
source: <0d132370-3e07-4332-bcfb-c4450100d736@ramsayjones.plus.com>
382
383
@@ -333,7 +414,7 @@ Release tarballs are available at:
414
415
Doc update.
416
336
- Will cook in 'next'.
417
+ Will merge to 'master'.
418
source: <20240715183739.7808-1-jltobler@gmail.com>
419
420
@@ -368,13 +449,11 @@ Release tarballs are available at:
449
A CI job that use clang-format to check coding style issues in new
450
code has been added.
451
371
- Will cook in 'next'.
452
+ Will merge to 'master'.
453
source: <20240723082111.874382-1-karthik.188@gmail.com>
454
455
375
-* rj/add-p-pager (2024-07-22) 6 commits
376
- - pager: make wait_for_pager a no-op for "cat"
377
- - t3701: avoid one-shot export for shell functions
456
+* rj/add-p-pager (2024-07-25) 4 commits
457
- add-patch: render hunks through the pager
458
- pager: introduce wait_for_pager
459
- pager: do not close fd 2 unnecessarily
@@ -382,9 +461,9 @@ Release tarballs are available at:
461
462
A 'P' command to "git add -p" that passes the patch hunk to the
463
pager has been added.
385
- source: <efa98aec-f117-4cfe-a7c2-e8c0adbdb399@gmail.com>
386
- source: <c37f0d54-4ead-422c-8193-f0c2ec84ca4a@gmail.com>
387
- source: <5536b336-5122-47fd-be57-42c299abe60c@gmail.com>
464
+
465
+ Will merge to 'next'.
466
+ source: <76936fb1-446d-455f-b4e7-6e24dda3c17d@gmail.com>
467
468
469
* ad/merge-with-diff-algorithm (2024-07-13) 1 commit
@@ -394,7 +473,7 @@ Release tarballs are available at:
473
Many Porcelain commands that internally use the merge machinery
474
were taught to consistently honor the diff.algorithm configuration.
475
397
- Will cook in 'next'.
476
+ Will merge to 'master'.
477
source: <pull.1743.v3.git.git.1720889507066.gitgitgadget@gmail.com>
478
479
@@ -407,7 +486,7 @@ Release tarballs are available at:
486
correct, but found confusing by some users. It now says that the
487
user needs to give pathspec to specify what paths to checkout.
488
410
- Will cook in 'next'.
489
+ Will merge to 'master'.
490
source: <xmqqikxnqzz4.fsf@gitster.g>
491
492
@@ -423,7 +502,7 @@ Release tarballs are available at:
502
503
Another reftable test has been ported to use the unit test framework.
504
426
- Will cook in 'next'.
505
+ Will merge to 'master'.
506
source: <20240712055041.6476-1-chandrapratap3519@gmail.com>
507
508
@@ -437,7 +516,7 @@ Release tarballs are available at:
516
517
Unit test clean-up.
518
440
- Will cook in 'next'.
519
+ Will merge to 'master'.
520
source: <35b0ba6b-d485-44f2-a19f-3ce816f8b435@web.de>
521
source: <983be396-f47c-4573-8c33-af8367f8ddbe@web.de>
522
source: <1521ed89-989e-452b-b7fc-9e73672e0764@web.de>
@@ -453,24 +532,24 @@ Release tarballs are available at:
532
source: <20240711235159.5320-1-shyamthakkar001@gmail.com>
533
534
456
-* rs/unit-tests-test-run (2024-07-23) 7 commits
457
- - unit-tests: show location of checks outside of tests
535
+* rs/unit-tests-test-run (2024-07-24) 7 commits
536
- t-strbuf: use for_test
537
- t-strvec: use for_test
538
- t-reftable-basics: use for_test
539
- t-ctype: use for_test
540
- unit-tests: add for_test
463
- - t0080: move expected output to a file
541
+ - unit-tests: show location of checks outside of tests
542
+ - t0080: use here-doc test body
543
544
Unit-test framework clean-up.
545
546
Still under discussion.
468
- source: <da7ed537-1c8e-42ec-aa91-49e1319e8c68@web.de>
547
+ source: <73465c3d-1be0-456b-9471-f875e819c566@web.de>
548
549
471
-* jc/patch-id (2024-06-21) 5 commits
472
- - patch-id: tighten code to detect the patch header
473
- - patch-id: rewrite code that detects the beginning of a patch
550
+* jc/patch-id (2024-07-29) 5 commits
551
+ . patch-id: tighten code to detect the patch header
552
+ . patch-id: rewrite code that detects the beginning of a patch
553
- patch-id: make get_one_patchid() more extensible
554
- patch-id: call flush_current_id() only when needed
555
- t4204: patch-id supports various input format
@@ -479,7 +558,7 @@ Release tarballs are available at:
558
getting confused by lines that look like a patch header in the log
559
message.
560
482
- Needs review.
561
+ Inviding further discussion.
562
source: <20240621231826.3280338-1-gitster@pobox.com>
563
564
--------------------------------------------------