What's cooking (2025/06 #05)
Junio C Hamano committed
Jun 15, 2025 at 22:44 UTC
b664de949fbe8e266c6e8078ac31d40a313606b7
1 file changed
+74
-68
whats-cooking.txt
+74
-68
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Jun 2025, #04; Thu, 12)
3
-X-master-at: 9edff09aec9b5aaa3d5528129bb279a4d34cf5b3
4
-X-next-at: 9a244e597829f0322c0da9a0f1a15fecc86eae1d
2
+Subject: What's cooking in git.git (Jun 2025, #05; Mon, 16)
3
+X-master-at: 16bd9f20a403117f2e0d9bcda6c6e621d3763e77
4
+X-next-at: 196bf9f422f28cd4e7989fb845ea6d2785c9953d
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Jun 2025, #04; Thu, 12)
7
+What's cooking in git.git (Jun 2025, #05; Mon, 16)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -17,14 +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
-We are almost done with this cycle. As we found out a ntohll
21
-regression that broke big endian boxes with builtin_bswap32/64
22
-supplied by their compilers way too late in the cycle, I'm planning
23
-to queue a revert for a single patch, which may or may not break
24
-Windows ARM64 support that was newly added during this cycle.
25
-Hopefully it is a better tradeoff for the entire Git community to
26
-drop support added by an unreleased product than to break a platform
27
-that has been working OK.
20
+Git 2.50 has been tagged. As the project usually is slow during
21
+Summer in Northern hemisphere, I plan to make the next cycle on the
22
+shorter side to last 8 weeks (usually a typical release cycle lasts
23
+for 8 to 12 weeks). Key dates are:
24
+
25
+ - Jun 23rd - the 2.51 cycle opens
26
+ - Aug 4th - 2.51-rc0 (preview)
27
+ - Aug 7th - 2.51-rc1 (master really freezes)
28
+ - Aug 13th - 2.51-rc2
29
+ - Aug 18th - 2.51-final
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
@@ -57,16 +59,43 @@ Release tarballs are available at:
59
--------------------------------------------------
60
[Graduated to 'master']
61
60
-* kh/maintenance-missing-tasks-docfix (2025-06-09) 1 commit
61
- (merged to 'next' on 2025-06-10 at 4d6d3d6af8)
62
- + doc: maintenance: fix linkgit syntax
62
+* jc/sed-build-fixes (2025-06-12) 1 commit
63
+ (merged to 'next' on 2025-06-12 at 4ad86fa8cf)
64
+ + build: sed portability fixes
65
+
66
+ Build fix.
67
+ source: <xmqqplf8evr9.fsf@gitster.g>
68
+
69
64
- Doc mark-up fix for a topic that has graduated to 'master'.
65
- source: <567195e5577c6c32b46f784a797fbf366873a0f3.1749484736.git.code@khaugsbakk.name>
70
+* js/github-ci-win-coverity-fix (2025-06-11) 2 commits
71
+ (merged to 'next' on 2025-06-12 at e0f5ed51f9)
72
+ + ci(coverity): output the build log upon error
73
+ + ci(coverity): fix building on Windows
74
+
75
+ Fixes for GitHub Actions Coverity job.
76
+ source: <pull.1934.v2.git.1749657278.gitgitgadget@gmail.com>
77
+
78
+
79
+* ss/revert-builtin-bswap-stuff (2025-06-11) 1 commit
80
+ (merged to 'next' on 2025-06-12 at fcaad0fe34)
81
+ + Revert "bswap.h: add support for built-in bswap functions"
82
+ (this branch is used by ss/compat-bswap-revamp.)
83
+
84
+ Revert a botched bswap.h change that broke ntohll() functions on
85
+ big-endian systems with __builtin_bswap32/64().
86
+ source: <20250611221444.1567638-2-sebastian@breakpoint.cc>
87
88
--------------------------------------------------
89
[New Topics]
90
91
+* jg/mailinfo-leakfix (2025-06-13) 1 commit
92
+ - mailinfo.c: fix memory leak in function handle_content_type()
93
+
94
+ source: <SA1PR22MB399911638F342E1AA20F014AE477A@SA1PR22MB3999.namprd22.prod.outlook.com>
95
+
96
+--------------------------------------------------
97
+[Cooking]
98
+
99
* ow/rebase-verify-insn-fmt-before-initializing-state (2025-06-09) 1 commit
100
- rebase: write script before initializing state
101
@@ -75,6 +104,7 @@ Release tarballs are available at:
104
leading to confused "git status"; this has been corrected.
105
106
Comments?
107
+ cf. <20250609221055.136074-1-oystwa@gmail.com>
108
source: <20250609221055.136074-1-oystwa@gmail.com>
109
110
@@ -91,78 +121,69 @@ Release tarballs are available at:
121
122
123
* ac/preload-index-wo-the-repository (2025-06-10) 2 commits
94
- - preload-index: stop depending on 'the_repository'
95
- - environment: remove the global variable 'core_preload_index'
124
+ (merged to 'next' on 2025-06-12 at c272b52078)
125
+ + preload-index: stop depending on 'the_repository'
126
+ + environment: remove the global variable 'core_preload_index'
127
128
Code clean-up.
129
99
- Will merge to 'next'?
130
+ Will cook in 'next'.
131
source: <cover.1749557133.git.ayu.chandekar@gmail.com>
132
133
134
* jc/cg-let-bss-do-its-job (2025-06-11) 1 commit
104
- - CodingGuidelines: let BSS do its job
135
+ (merged to 'next' on 2025-06-12 at 951bdd6678)
136
+ + CodingGuidelines: let BSS do its job
137
138
Clarify "do not explicitly initialize to zero" rule in the
139
CodingGuidelines document.
140
109
- Will merge to 'next'.
141
+ Will cook in 'next'.
142
source: <xmqqh60mger9.fsf@gitster.g>
143
144
113
-* jc/merge-compact-summary (2025-06-11) 2 commits
145
+* jc/merge-compact-summary (2025-06-12) 2 commits
146
- merge/pull: extend merge.stat configuration variable to cover --compact-summary
115
- - merge/pull: --compact-summary
147
+ - merge/pull: add the "--compact-summary" option
148
149
+ "git merge/pull" has been taught the "--compact-summary" option to
150
+ use the compact-summary format, intead of diffstat, when showing
151
+ the summary of the incoming changes.
152
118
-* js/github-ci-win-coverity-fix (2025-06-11) 2 commits
119
- - ci(coverity): output the build log upon error
120
- - ci(coverity): fix building on Windows
121
-
122
- Fixes for GitHub Actions Coverity job.
123
-
124
- Will merge to 'next' and then to 'master'.
125
- source: <pull.1934.v2.git.1749657278.gitgitgadget@gmail.com>
153
+ Will merge to 'next'?
154
+ source: <20250612222537.2426059-1-gitster@pobox.com>
155
156
157
* ly/prepare-show-merge-leakfix (2025-06-09) 1 commit
129
- - revision: fix memory leak in prepare_show_merge()
158
+ (merged to 'next' on 2025-06-12 at 518d60458f)
159
+ + revision: fix memory leak in prepare_show_merge()
160
161
Leakfix.
162
133
- Will merge to 'next'.
163
+ Will cook in 'next'.
164
source: <pull.1989.v3.git.git.1749515879546.gitgitgadget@gmail.com>
165
166
137
-* sa/multi-mailmap-fix (2025-06-10) 1 commit
138
- - cat-file: fix mailmap application for different author and committer
167
+* sa/multi-mailmap-fix (2025-06-13) 1 commit
168
+ (merged to 'next' on 2025-06-13 at 739626bc46)
169
+ + cat-file: fix mailmap application for different author and committer
170
171
When asking to apply mailmap to both author and committer field
172
while showing a commit object, the field that appears later was not
173
correctly parsed and replaced, which has been corrected.
174
144
- Will merge to 'next'?
145
- source: <20250611062643.8639-1-siddharthasthana31@gmail.com>
175
+ Will cook in 'next'.
176
+ source: <20250613115750.41205-1-siddharthasthana31@gmail.com>
177
178
148
-* bs/config-mak-freebsd (2025-06-11) 1 commit
179
+* bs/config-mak-freebsd (2025-06-12) 1 commit
180
- config.mak.uname: update settings for FreeBSD
181
182
Drop FreeBSD 4 support and assume we are at least at FreeBSD 6 with
183
memmem() supported.
184
154
- Need to pick up a reroll?
155
- source: <aEpZXqTOForaZzbf@humpty.home.comstyle.com>
156
-
157
-
158
-* jc/sed-build-fixes (2025-06-12) 1 commit
159
- (merged to 'next' on 2025-06-12 at 4ad86fa8cf)
160
- + build: sed portability fixes
161
-
162
- Build fix.
163
-
164
- Will merge to 'master'.
165
- source: <xmqqplf8evr9.fsf@gitster.g>
185
+ Expecting a finalized version from Carlo?
186
+ source: <xmqqv7p0bpdl.fsf_-_@gitster.g>
187
188
189
* jc/tag-idempotent-no-op (2025-06-10) 1 commit
@@ -183,7 +204,6 @@ Release tarballs are available at:
204
- bswap.h: define GIT_LITTLE_ENDIAN on MSVC as little endian
205
- bswap.h: add support for __BYTE_ORDER__
206
- Merge branch 'ss/revert-builtin-bswap-stuff' into ss/compat-bswap-revamp
186
- (this branch uses ss/revert-builtin-bswap-stuff.)
207
208
Clean-up compat/bswap.h mess.
209
@@ -191,20 +211,6 @@ Release tarballs are available at:
211
source: <20250611221444.1567638-1-sebastian@breakpoint.cc>
212
213
194
-* ss/revert-builtin-bswap-stuff (2025-06-11) 1 commit
195
- (merged to 'next' on 2025-06-12 at fcaad0fe34)
196
- + Revert "bswap.h: add support for built-in bswap functions"
197
- (this branch is used by ss/compat-bswap-revamp.)
198
-
199
- Revert a botched bswap.h change that broke ntohll() functions on
200
- big-endian systems with __builtin_bswap32/64().
201
-
202
- Will merge to 'master'.
203
- source: <20250611221444.1567638-2-sebastian@breakpoint.cc>
204
-
205
---------------------------------------------------
206
-[Cooking]
207
-
214
* ja/doc-git-log-markup (2025-06-08) 9 commits
215
- doc: git-log: convert log config to new doc format
216
- doc: git-log: convert diff options to new doc format
@@ -243,7 +249,7 @@ Release tarballs are available at:
249
source: <pull.1987.git.git.1749355019495.gitgitgadget@gmail.com>
250
251
246
-* kn/fetch-push-bulk-ref-update-fixup (2025-06-06) 3 commits
252
+* kn/fetch-push-bulk-ref-update-fixup (2025-06-13) 3 commits
253
- receive-pack: handle reference deletions separately
254
- refs/files: skip updates with errors in batched updates
255
- Merge branch 'kn/fetch-push-bulk-ref-update' into kn/fetch-push-bulk-ref-update-fixup
@@ -252,7 +258,7 @@ Release tarballs are available at:
258
Additional fixes to the base topic.
259
260
Comments?
255
- source: <20250606-6769-address-test-failures-in-the-next-branch-caused-by-batched-reference-updates-v3-0-e1c41693bd35@gmail.com>
261
+ source: <20250613-6769-address-test-failures-in-the-next-branch-caused-by-batched-reference-updates-v4-0-ebf53edb9795@gmail.com>
262
263
264
* ma/doc-diff-cc-headers (2025-06-06) 1 commit