What's cooking (2023/04 #09)
Junio C Hamano committed
Apr 28, 2023 at 16:44 UTC
c8bd5503acc9605a7f4671f3dee361bc26da5ff0
1 file changed
+101
-119
whats-cooking.txt
+101
-119
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Apr 2023, #08; Thu, 27)
3
-X-master-at: f85cd430b12b0d3e4f1a30ef3239a1b73d5f6331
4
-X-next-at: f1e218fcd8619b15a0125c091d4134e60ed764f1
2
+Subject: What's cooking in git.git (Apr 2023, #09; Fri, 28)
3
+X-master-at: 48d89b51b3bb8a60580c36731b96a7206ce1e5b9
4
+X-next-at: e96c925001b196247b94383a62a3b9781b57df80
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Apr 2023, #08; Thu, 27)
7
+What's cooking in git.git (Apr 2023, #09; Fri, 28)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -16,9 +16,6 @@ message that raises issues but they are no means exhaustive. A
16
topic without enough support may be discarded after a long period of
17
no activity.
18
19
-A set of new maintenance releases to address some security issues
20
-have been made; all the integration tracks also have the same fixes.
21
-
19
Copies of the source code to Git live in many repositories, and the
20
following is a list of the ones I push into or their mirrors. Some
21
repositories have only a subset of branches.
@@ -50,92 +47,77 @@ Release tarballs are available at:
47
--------------------------------------------------
48
[Graduated to 'master']
49
53
-* ds/fsck-pack-revindex (2023-04-17) 5 commits
54
- (merged to 'next' on 2023-04-19 at 6fb9527bf5)
55
- + fsck: validate .rev file header
56
- + fsck: check rev-index position values
57
- + fsck: check rev-index checksums
58
- + fsck: create scaffolding for rev-index checks
59
- + Merge branch 'tb/pack-revindex-on-disk' into ds/fsck-pack-revindex
60
- (this branch uses tb/pack-revindex-on-disk.)
61
-
62
- "git fsck" learned to validate the on-disk pack reverse index files.
63
- source: <pull.1512.git.1681748502.gitgitgadget@gmail.com>
64
-
50
+* jk/gpg-trust-level-fix (2023-04-19) 1 commit
51
+ (merged to 'next' on 2023-04-21 at eb8413dc9d)
52
+ + gpg-interface: set trust level of missing key to "undefined"
53
66
-* fc/doc-checkout-markup-updates (2023-04-18) 2 commits
67
- (merged to 'next' on 2023-04-20 at 62782d75c4)
68
- + doc: git-checkout: reorganize examples
69
- + doc: git-checkout: trivial callout cleanup
54
+ The "%GT" placeholder for the "--format" option of "git log" and
55
+ friends caused BUG() to trigger on a commit signed with an unknown
56
+ key, which has been corrected.
57
+ source: <20230419012957.GA503941@coredump.intra.peff.net>
58
71
- Doc mark-up update.
72
- source: <20230418070048.2209469-1-felipe.contreras@gmail.com>
59
60
+* tb/enable-cruft-packs-by-default (2023-04-18) 10 commits
61
+ (merged to 'next' on 2023-04-21 at 068bf86fc3)
62
+ + repository.h: drop unused `gc_cruft_packs`
63
+ + builtin/gc.c: make `gc.cruftPacks` enabled by default
64
+ + t/t9300-fast-import.sh: prepare for `gc --cruft` by default
65
+ + t/t6500-gc.sh: add additional test cases
66
+ + t/t6500-gc.sh: refactor cruft pack tests
67
+ + t/t6501-freshen-objects.sh: prepare for `gc --cruft` by default
68
+ + t/t5304-prune.sh: prepare for `gc --cruft` by default
69
+ + builtin/gc.c: ignore cruft packs with `--keep-largest-pack`
70
+ + builtin/repack.c: fix incorrect reference to '-C'
71
+ + pack-write.c: plug a leak in stage_tmp_packfiles()
72
75
-* fc/doc-use-datestamp-in-commit (2023-04-14) 3 commits
76
- (merged to 'next' on 2023-04-20 at 3b6ccb62ec)
77
- + doc: set actual revdate for manpages
78
- + Merge branch 'fc/doc-stop-using-manversion' into fc/doc-use-datestamp-in-commit
79
- + Merge branch 'fc/remove-header-workarounds-for-asciidoc' into fc/doc-use-datestamp-in-commit
73
+ When "gc" needs to retain unreachable objects, packing them into
74
+ cruft packs (instead of exploding them into loose object files) has
75
+ been offered as a more efficient option for some time. Now the use
76
+ of cruft packs has been made the default and no longer considered
77
+ an experimental feature.
78
+ source: <cover.1681850424.git.me@ttaylorr.com>
79
81
- Instead of the time the formatter was run, show the timestamp
82
- recorded in the commit in the documentation.
83
- source: <20230413074722.71260-1-felipe.contreras@gmail.com>
80
+--------------------------------------------------
81
+[New Topics]
82
83
+* ah/doc-attributes-text (2023-04-28) 1 commit
84
+ - docs: rewrite the documentation of the text and eol attributes
85
86
-* tb/pack-revindex-on-disk (2023-04-13) 7 commits
87
- (merged to 'next' on 2023-04-19 at d6b90b44cf)
88
- + t: invert `GIT_TEST_WRITE_REV_INDEX`
89
- + config: enable `pack.writeReverseIndex` by default
90
- + pack-revindex: introduce `pack.readReverseIndex`
91
- + pack-revindex: introduce GIT_TEST_REV_INDEX_DIE_ON_DISK
92
- + pack-revindex: make `load_pack_revindex` take a repository
93
- + t5325: mark as leak-free
94
- + pack-write.c: plug a leak in stage_tmp_packfiles()
95
- (this branch is used by ds/fsck-pack-revindex.)
86
+ Doc update to clarify how text and eol attributes interact to
87
+ specify the end-of-line conversion.
88
97
- The on-disk reverse index that allows mapping from the pack offset
98
- to the object name for the object stored at the offset has been
99
- enabled by default.
100
- source: <cover.1681338013.git.me@ttaylorr.com>
89
+ Needs review.
90
+ source: <20230428042221.871095-1-alexhenrie24@gmail.com>
91
102
---------------------------------------------------
103
-[New Topics]
92
105
-* hx/negotiator-non-recursive (2023-04-26) 2 commits
106
- - negotiator/skipping: fix some problems in mark_common()
107
- - negotiator/default: avoid stack overflow
93
+* jw/send-email-update-gmail-insn (2023-04-28) 1 commit
94
+ - send-email docs: Remove mention of discontinued gmail feature
95
109
- The implementation of the default "negotiator", used to find common
110
- ancestor over the network for object tranfer, used to be recursive;
111
- it was updated to be iterative to conserve stackspace usage.
96
+ Doc update to drop use of deprecated app-specific password against
97
+ gmail.
98
113
- Comments?
114
- source: <cover.1682513384.git.hanxin.hx@bytedance.com>
99
+ Will merge to 'next'.
100
+ source: <20221001104609.18453-1-j.witteveen@gmail.com>
101
102
117
-* jc/doc-clarify-git-default-hash-variable (2023-04-26) 1 commit
118
- - doc: GIT_DEFAULT_HASH is and will be ignored during "clone"
103
+* ob/messages-capitalize-exception (2023-04-28) 1 commit
104
+ - messages: capitalization and punctuation exceptions
105
+ (this branch uses ob/sequencer-i18n-fix.)
106
120
- The documentation was misleading about the interaction between
121
- GIT_DEFAULT_HASH and "git clone", which has been clarified to
122
- stress that the variable is to be ignored by the command.
107
+ Message update.
108
124
- Will merge to 'next'?
125
- source: <xmqqzg6uvfpo.fsf_-_@gitster.g>
109
+ Will merge to 'next'.
110
+ source: <20230428125649.1719796-1-oswald.buddenhagen@gmx.de>
111
112
128
-* mh/fix-detect-compilers-with-nondigit-versions (2023-04-26) 1 commit
129
- - Handle some compiler versions containing a dash
113
+* ob/sequencer-i18n-fix (2023-04-28) 1 commit
114
+ - sequencer: actually translate report in do_exec()
115
+ (this branch is used by ob/messages-capitalize-exception.)
116
131
- The detect-compilers script to help auto-tweaking the build system
132
- had trouble working with compilers whose version number has extra
133
- suffixes. The script has been taught that certain suffixes (like
134
- "-win32" in "gcc 10-win32") can be safely stripped as they share
135
- the same features and bugs with the version without the suffix.
117
+ Message update.
118
119
Will merge to 'next'.
138
- source: <20230426004843.3391826-1-mh@glandium.org>
120
+ source: <20230428125649.1719796-2-oswald.buddenhagen@gmx.de>
121
122
--------------------------------------------------
123
[Stalled]
@@ -293,7 +275,44 @@ Release tarballs are available at:
275
--------------------------------------------------
276
[Cooking]
277
296
-* tl/notes-separator (2023-04-25) 6 commits
278
+* hx/negotiator-non-recursive (2023-04-26) 2 commits
279
+ - negotiator/skipping: fix some problems in mark_common()
280
+ - negotiator/default: avoid stack overflow
281
+
282
+ The implementation of the default "negotiator", used to find common
283
+ ancestor over the network for object tranfer, used to be recursive;
284
+ it was updated to be iterative to conserve stackspace usage.
285
+
286
+ Comments?
287
+ source: <cover.1682513384.git.hanxin.hx@bytedance.com>
288
+
289
+
290
+* jc/doc-clarify-git-default-hash-variable (2023-04-26) 1 commit
291
+ - doc: GIT_DEFAULT_HASH is and will be ignored during "clone"
292
+
293
+ The documentation was misleading about the interaction between
294
+ GIT_DEFAULT_HASH and "git clone", which has been clarified to
295
+ stress that the variable is to be ignored by the command.
296
+
297
+ Will merge to 'next'?
298
+ source: <xmqqzg6uvfpo.fsf_-_@gitster.g>
299
+
300
+
301
+* mh/fix-detect-compilers-with-nondigit-versions (2023-04-26) 1 commit
302
+ (merged to 'next' on 2023-04-28 at c0c54291c2)
303
+ + Handle some compiler versions containing a dash
304
+
305
+ The detect-compilers script to help auto-tweaking the build system
306
+ had trouble working with compilers whose version number has extra
307
+ suffixes. The script has been taught that certain suffixes (like
308
+ "-win32" in "gcc 10-win32") can be safely stripped as they share
309
+ the same features and bugs with the version without the suffix.
310
+
311
+ Will merge to 'master'.
312
+ source: <20230426004843.3391826-1-mh@glandium.org>
313
+
314
+
315
+* tl/notes-separator (2023-04-28) 6 commits
316
- notes.c: introduce "--[no-]stripspace" option
317
- notes.c: append separator instead of insert by pos
318
- notes.c: introduce '--separator=<paragraph-break>' option
@@ -306,7 +325,7 @@ Release tarballs are available at:
325
326
Will merge to 'next'?
327
Looking good.
309
- source: <cover.1682429602.git.dyroneteng@gmail.com>
328
+ source: <cover.1682671758.git.dyroneteng@gmail.com>
329
330
331
* ek/completion-use-read-r-to-read-literally (2023-04-20) 1 commit
@@ -361,16 +380,17 @@ Release tarballs are available at:
380
381
382
* jk/parse-commit-with-malformed-ident (2023-04-27) 4 commits
364
- - parse_commit(): describe more date-parsing failure modes
365
- - parse_commit(): handle broken whitespace-only timestamp
366
- - parse_commit(): parse timestamp from end of line
367
- - t4212: avoid putting git on left-hand side of pipe
383
+ (merged to 'next' on 2023-04-28 at cb6ea0412a)
384
+ + parse_commit(): describe more date-parsing failure modes
385
+ + parse_commit(): handle broken whitespace-only timestamp
386
+ + parse_commit(): parse timestamp from end of line
387
+ + t4212: avoid putting git on left-hand side of pipe
388
389
The commit object parser has been taught to be a bit more lenient
390
to parse timestamps on the author/committer line with a malformed
391
author/committer ident.
392
373
- Will merge to 'next'.
393
+ Will merge to 'master'.
394
source: <20230427081330.GA1461786@coredump.intra.peff.net>
395
396
@@ -432,18 +452,6 @@ Release tarballs are available at:
452
source: <pull.1517.v2.git.1682194649.gitgitgadget@gmail.com>
453
454
435
-* jk/gpg-trust-level-fix (2023-04-19) 1 commit
436
- (merged to 'next' on 2023-04-21 at eb8413dc9d)
437
- + gpg-interface: set trust level of missing key to "undefined"
438
-
439
- The "%GT" placeholder for the "--format" option of "git log" and
440
- friends caused BUG() to trigger on a commit signed with an unknown
441
- key, which has been corrected.
442
-
443
- Will merge to 'master'.
444
- source: <20230419012957.GA503941@coredump.intra.peff.net>
445
-
446
-
455
* ps/fetch-output-format (2023-04-27) 8 commits
456
- fetch: introduce machine-parseable "porcelain" output format
457
- fetch: introduce new `--output-format` option
@@ -482,29 +490,6 @@ Release tarballs are available at:
490
source: <20230420205350.600760-1-szeder.dev@gmail.com>
491
492
485
-* tb/enable-cruft-packs-by-default (2023-04-18) 10 commits
486
- (merged to 'next' on 2023-04-21 at 068bf86fc3)
487
- + repository.h: drop unused `gc_cruft_packs`
488
- + builtin/gc.c: make `gc.cruftPacks` enabled by default
489
- + t/t9300-fast-import.sh: prepare for `gc --cruft` by default
490
- + t/t6500-gc.sh: add additional test cases
491
- + t/t6500-gc.sh: refactor cruft pack tests
492
- + t/t6501-freshen-objects.sh: prepare for `gc --cruft` by default
493
- + t/t5304-prune.sh: prepare for `gc --cruft` by default
494
- + builtin/gc.c: ignore cruft packs with `--keep-largest-pack`
495
- + builtin/repack.c: fix incorrect reference to '-C'
496
- + pack-write.c: plug a leak in stage_tmp_packfiles()
497
-
498
- When "gc" needs to retain unreachable objects, packing them into
499
- cruft packs (instead of exploding them into loose object files) has
500
- been offered as a more efficient option for some time. Now the use
501
- of cruft packs has been made the default and no longer considered
502
- an experimental feature.
503
-
504
- Will merge to 'master'.
505
- source: <cover.1681850424.git.me@ttaylorr.com>
506
-
507
-
493
* ms/send-email-feed-header-to-validate-hook (2023-04-19) 2 commits
494
- send-email: expose header information to git-send-email's sendemail-validate hook
495
- send-email: refactor header generation functions
@@ -531,15 +516,12 @@ Release tarballs are available at:
516
source: <20230417093255.31079-1-jacobabel@nullpo.dev>
517
518
534
-* gc/doc-cocci-updates (2023-04-12) 2 commits
519
+* gc/doc-cocci-updates (2023-04-27) 2 commits
520
- cocci: codify authoring and reviewing practices
521
- cocci: add headings to and reword README
522
523
Update documentation regarding Coccinelle patches.
539
-
540
- Expecting review response.
541
- cf. <xmqqmt3by5sc.fsf@gitster.g>
542
- source: <pull.1495.git.git.1681329955.gitgitgadget@gmail.com>
524
+ source: <pull.1495.v2.git.git.1682634143.gitgitgadget@gmail.com>
525
526
527
* kh/doc-interpret-trailers-updates (2023-04-12) 4 commits