What's cooking (2024/04 #01)
Junio C Hamano committed
Apr 1, 2024 at 11:38 UTC
4b384fc6115878c90ed1eb549d021d4b56d5cfb6
1 file changed
+105
-106
whats-cooking.txt
+105
-106
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Mar 2024, #09; Thu, 28)
2
+Subject: What's cooking in git.git (Apr 2024, #01; Mon, 1)
3
X-master-at: d6fd04375f9196f8b203d442f235bd96a1a068cc
4
X-next-at: 09a8706636d10c491176b8b1cd6519f7300911bf
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Mar 2024, #09; Thu, 28)
7
+What's cooking in git.git (Apr 2024, #01; Mon, 1)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -27,7 +27,7 @@ With maint, master, next, seen, todo:
27
git://repo.or.cz/alt-git.git/
28
https://kernel.googlesource.com/pub/scm/git/git/
29
https://github.com/git/git/
30
- https://gitlab.com/git-vcs/git/
30
+ https://gitlab.com/git-scm/git/
31
32
With all the integration branches and topics broken out:
33
@@ -46,101 +46,99 @@ Release tarballs are available at:
46
https://www.kernel.org/pub/software/scm/git/
47
48
--------------------------------------------------
49
-[Graduated to 'master']
50
-
51
-* bt/fuzz-config-parse (2024-03-15) 1 commit
52
- (merged to 'next' on 2024-03-21 at 6e9f331d68)
53
- + fuzz: add fuzzer for config parsing
54
-
55
- A new fuzz target that exercises config parsing code has been
56
- added.
57
- source: <pull.1692.v2.git.1710481652130.gitgitgadget@gmail.com>
58
-
59
-
60
-* eb/hash-transition (2023-10-02) 30 commits
61
- (merged to 'next' on 2024-03-11 at 9cff2e4ab7)
62
- + t1016-compatObjectFormat: add tests to verify the conversion between objects
63
- + t1006: test oid compatibility with cat-file
64
- + t1006: rename sha1 to oid
65
- + test-lib: compute the compatibility hash so tests may use it
66
- + builtin/ls-tree: let the oid determine the output algorithm
67
- + object-file: handle compat objects in check_object_signature
68
- + tree-walk: init_tree_desc take an oid to get the hash algorithm
69
- + builtin/cat-file: let the oid determine the output algorithm
70
- + rev-parse: add an --output-object-format parameter
71
- + repository: implement extensions.compatObjectFormat
72
- + object-file: update object_info_extended to reencode objects
73
- + object-file-convert: convert commits that embed signed tags
74
- + object-file-convert: convert commit objects when writing
75
- + object-file-convert: don't leak when converting tag objects
76
- + object-file-convert: convert tag objects when writing
77
- + object-file-convert: add a function to convert trees between algorithms
78
- + object: factor out parse_mode out of fast-import and tree-walk into in object.h
79
- + cache: add a function to read an OID of a specific algorithm
80
- + tag: sign both hashes
81
- + commit: export add_header_signature to support handling signatures on tags
82
- + commit: convert mergetag before computing the signature of a commit
83
- + commit: write commits for both hashes
84
- + object-file: add a compat_oid_in parameter to write_object_file_flags
85
- + object-file: update the loose object map when writing loose objects
86
- + loose: compatibilty short name support
87
- + loose: add a mapping between SHA-1 and SHA-256 for loose objects
88
- + repository: add a compatibility hash algorithm
89
- + object-names: support input of oids in any supported hash
90
- + oid-array: teach oid-array to handle multiple kinds of oids
91
- + object-file-convert: stubs for converting from one object format to another
92
-
93
- Work to support a repository that work with both SHA-1 and SHA-256
94
- hash algorithms has started.
95
- source: <878r8l929e.fsf@gmail.froward.int.ebiederm.org>
96
-
97
-
98
-* jc/show-untracked-false (2024-03-13) 2 commits
99
- (merged to 'next' on 2024-03-21 at 6d1f5603c6)
100
- + status: allow --untracked=false and friends
101
- + status: unify parsing of --untracked= and status.showUntrackedFiles
102
-
103
- The status.showUntrackedFiles configuration variable had a name
104
- that tempts users to set a Boolean value expressed in our usual
105
- "false", "off", and "0", but it only took "no". This has been
106
- corrected so "true" and its synonyms are taken as "normal", while
107
- "false" and its synonyms are taken as "no".
108
- source: <20240313173214.962532-1-gitster@pobox.com>
109
-
110
-
111
-* jk/drop-hg-to-git (2024-03-20) 1 commit
112
- (merged to 'next' on 2024-03-21 at 603d614310)
113
- + contrib: drop hg-to-git script
114
-
115
- Remove an ancient and not well maintained Hg-to-git migration
116
- script from contrib/.
117
-
118
- Acked-by: Stelian Pop <stelian@popies.net>
119
- cf. <37e4cd61-b370-437e-bd42-f98f47d3ad32@popies.net>
120
- source: <20240320094824.GA2445978@coredump.intra.peff.net>
121
-
122
-
123
-* ph/diff-src-dst-prefix-config (2024-03-18) 2 commits
124
- (merged to 'next' on 2024-03-21 at 96801520db)
125
- + diff.*Prefix: use camelCase in the doc and test titles
126
- + diff: add diff.srcPrefix and diff.dstPrefix configuration variables
127
-
128
- "git diff" and friends learned two extra configuration variables,
129
- diff.srcPrefix and diff.dstPrefix.
130
- source: <20240315010310.GA1901653@quokka>
131
- source: <xmqq8r2ioh19.fsf@gitster.g>
132
-
133
-
134
-* rs/t-prio-queue-fixes (2024-03-18) 2 commits
135
- (merged to 'next' on 2024-03-21 at 0730741187)
136
- + t-prio-queue: check result array bounds
137
- + t-prio-queue: shorten array index message
138
-
139
- Test clean-up.
140
- source: <9bf36cc8-ff27-44df-b2fb-9f959c781269@web.de>
49
+[New Topics]
50
+
51
+* es/test-cron-safety (2024-03-31) 1 commit
52
+ - test-lib: fix non-functioning GIT_TEST_MAINT_SCHEDULER fallback
53
+
54
+ The test script had an incomplete and ineffective attempt to avoid
55
+ clobbering the testing user's real crontab (and its equivalents),
56
+ which has been completed.
57
+
58
+ Will merge to 'next'.
59
+ source: <20240329222703.9343-1-ericsunshine@charter.net>
60
+
61
+
62
+* gt/add-u-commit-i-pathspec-check (2024-03-29) 3 commits
63
+ - builtin/add: error out when passing untracked path with -u
64
+ - builtin/commit: error out when passing untracked path with -i
65
+ - read-cache: optionally collect pathspec matching info
66
+
67
+ "git add -u <pathspec>" and "git commit [-i] <pathspec>" did not
68
+ diagnose a pathspec element that did not match any files in certain
69
+ situations, unlike "git add <pathspec>" did.
70
+
71
+ Comments?
72
+ source: <20240318155219.494206-2-shyamthakkar001@gmail.com>
73
+
74
+
75
+* jc/advice-sans-trailing-whitespace (2024-03-29) 1 commit
76
+ - advice: omit trailing whitespace
77
+
78
+ The "hint:" messages given by the advice mechanism, when given a
79
+ message with a blank line, left a line with trailing whitespace,
80
+ which has been cleansed.
81
+
82
+ Will merge to 'next'.
83
+ source: <xmqq4jcooddp.fsf@gitster.g>
84
+
85
+
86
+* jt/reftable-geometric-compaction (2024-03-29) 3 commits
87
+ - reftable/stack: make segment end inclusive
88
+ - reftable/stack: use geometric table compaction
89
+ - reftable/stack: add env to disable autocompaction
90
+
91
+ The strategy to compat multiple tables of reftables after many
92
+ operations accumulate many entries has been improved to avoid
93
+ accumulating too many tables uncollected.
94
+
95
+ Will merge to 'next'?
96
+ cf. <Zfzd_yxeXWWTJdyP@tanuki>
97
+ source: <pull.1683.v3.git.1711685809.gitgitgadget@gmail.com>
98
+
99
+
100
+* ds/typofix-core-config-doc (2024-03-31) 1 commit
101
+ - config: fix some small capitalization issues, as spotted
102
+
103
+ Typofix.
104
+
105
+ Will merge to 'next'.
106
+ source: <26135b06c48565ee8ac6dcfc1ef5431511e6202c.1711918168.git.dsimic@manjaro.org>
107
+
108
+
109
+* jc/checkout-detach-wo-tracking-report (2024-03-30) 1 commit
110
+ - checkout: omit "tracking" information on a detached HEAD
111
+
112
+ "git checkout/switch --detach foo", after switching to the detached
113
+ HEAD state, gave the tracking information for the 'foo' branch,
114
+ which was pointless.
115
+
116
+ Comments?
117
+ source: <xmqqa5mfl7ud.fsf@gitster.g>
118
+
119
+
120
+* rj/use-adv-if-enabled (2024-03-30) 3 commits
121
+ - add: use advise_if_enabled for ADVICE_ADD_EMBEDDED_REPO
122
+ - add: use advise_if_enabled for ADVICE_ADD_EMPTY_PATHSPEC
123
+ - add: use advise_if_enabled for ADVICE_ADD_IGNORED_FILE
124
+
125
+ Use advice_if_enabled() API to rewrite a simple pattern to
126
+ call advise() after checking advice_enabled().
127
+
128
+ Will merge to 'next'?
129
+ source: <46fba030-d7aa-49d2-88fa-e506850f7b6a@gmail.com>
130
+
131
+
132
+* rs/mem-pool-size-t-safety (2024-03-31) 1 commit
133
+ - mem-pool: use st_add() in mem_pool_strvfmt()
134
+
135
+ size_t arithmetic safety.
136
+
137
+ Will merge to 'next'.
138
+ source: <bbe00b9e-64d8-4ec8-a2b9-2c6917c72dbd@web.de>
139
140
--------------------------------------------------
143
-[New Topics]
141
+[Cooking]
142
143
* ew/khash-to-khashl (2024-03-28) 3 commits
144
- khashl: fix ensemble lookups on empty table
@@ -172,7 +170,7 @@ Release tarballs are available at:
170
source: <cover.1711519925.git.ps@pks.im>
171
172
175
-* rj/add-p-explicit-reshow (2024-03-28) 2 commits
173
+* rj/add-p-explicit-reshow (2024-03-29) 2 commits
174
- add-patch: do not print hunks repeatedly
175
- add-patch: introduce 'p' in interactive-patch
176
@@ -181,10 +179,8 @@ Release tarballs are available at:
179
an additional action to explicitly ask to reshow the current hunk.
180
181
Will merge to 'next'?
184
- source: <60d978d0-f69a-4b65-b4ba-d30dac8f112a@gmail.com>
182
+ source: <a9c515fe-6664-4b5d-abca-d88fdd32a883@gmail.com>
183
186
---------------------------------------------------
187
-[Cooking]
184
185
* az/grep-group-error-message-update (2024-03-25) 1 commit
186
(merged to 'next' on 2024-03-27 at 567bf00ed4)
@@ -244,8 +240,9 @@ Release tarballs are available at:
240
source: <cover.1711398665.git.dsimic@manjaro.org>
241
242
247
-* ja/doc-markup-updates (2024-03-25) 4 commits
248
- - doc: git-clone: apply new documentation guidelines
243
+* ja/doc-markup-updates (2024-03-29) 5 commits
244
+ - doc: git-clone: do not autoreference the manpage in itself
245
+ - doc: git-clone: apply new documentation formatting guidelines
246
- doc: git-init: apply new documentation formatting guidelines
247
- doc: allow literal and emphasis format in doc vs help tests
248
- doc: rework CodingGuidelines with new formatting rules
@@ -254,7 +251,7 @@ Release tarballs are available at:
251
literal parts and a few manual pages have been updated as examples.
252
253
Will merge to 'next'?
257
- source: <pull.1702.git.1711318739.gitgitgadget@gmail.com>
254
+ source: <pull.1702.v2.git.1711711181.gitgitgadget@gmail.com>
255
256
257
* mg/editorconfig-makefile (2024-03-23) 1 commit
@@ -437,7 +434,8 @@ Release tarballs are available at:
434
source: <cover.1711001016.git.dsimic@manjaro.org>
435
436
440
-* jc/apply-parse-diff-git-header-names-fix (2024-03-28) 2 commits
437
+* jc/apply-parse-diff-git-header-names-fix (2024-03-29) 3 commits
438
+ - t4126: fix "funny directory name" test on Windows (again)
439
(merged to 'next' on 2024-03-28 at a35de15836)
440
+ t4126: make sure a directory with SP at the end is usable
441
(merged to 'next' on 2024-03-27 at d586367985)
@@ -447,9 +445,10 @@ Release tarballs are available at:
445
when the change was about an empty file created in or deleted from
446
a directory whose name ends with a SP, which has been corrected.
447
450
- Will merge to 'master'.
451
- source: <xmqqh6gqt674.fsf_-_@gitster.g>
448
+ Will merge to 'next'?
449
source: <xmqqfrwlltjn.fsf@gitster.g>
450
+ source: <xmqqh6gqt674.fsf_-_@gitster.g>
451
+ source: <xmqq5xx50x8p.fsf_-_@gitster.g>
452
453
454
* jk/pretty-subject-cleanup (2024-03-22) 7 commits