What's cooking (2025/09 #08)
Junio C Hamano committed
Sep 19, 2025 at 12:59 UTC
731d556c769dacc83c983de9b87236db5afd2757
1 file changed
+276
-220
whats-cooking.txt
+276
-220
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Sep 2025, #07; Wed, 17)
3
-X-master-at: 215033b3ac599432a17d58f18a92b356d98354a9
4
-X-next-at: 15c5d4f767f655d8c09d24948ad0ab2a5e304793
2
+Subject: What's cooking in git.git (Sep 2025, #08; Fri, 19)
3
+X-master-at: ca2559c1d630eb4f04cdee2328aaf1c768907a9e
4
+X-next-at: c4e3cb95175ecb4a955ccff0899fd16de0cea8e8
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Sep 2025, #07; Wed, 17)
7
+What's cooking in git.git (Sep 2025, #08; Fri, 19)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -17,11 +17,6 @@ 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
-There are a few topics that have been expecting a reroll for close
21
-to a month. I've moved them to the [Stalled] section below. Let's
22
-tighten rules around these topics a bit so that we can keep the tree
23
-somewhat cleaner.
24
-
20
Copies of the source code to Git live in many repositories, and the
21
following is a list of the ones I push into or their mirrors. Some
22
repositories have only a subset of branches.
@@ -50,9 +45,231 @@ Release tarballs are available at:
45
46
https://www.kernel.org/pub/software/scm/git/
47
48
+--------------------------------------------------
49
+[Graduated to 'master']
50
+
51
+* ag/doc-sendmail-gmail-example-update (2025-08-26) 1 commit
52
+ (merged to 'next' on 2025-09-12 at 54e0dab4b0)
53
+ + docs: update sendmail docs to use more secure SMTP server for Gmail
54
+
55
+ Doc update.
56
+ source: <20250826150919.5239-1-gargaditya08@live.com>
57
+
58
+
59
+* ag/send-email-imap-sent (2025-08-11) 2 commits
60
+ (merged to 'next' on 2025-09-12 at bb82691e0a)
61
+ + send-email: enable copying emails to an IMAP folder without actually sending them
62
+ + send-email: add ability to send a copy of sent emails to an IMAP folder
63
+
64
+ "git send-email" learned to drive "git imap-send" to store already
65
+ sent e-mails in an IMAP folder.
66
+ source: <PN3PR01MB9597E8E33868386C997D2563B82BA@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM>
67
+
68
+
69
+* jc/doc-includeif-hasconfig-remote-url-fix (2025-08-21) 1 commit
70
+ (merged to 'next' on 2025-09-12 at 3b91910cbd)
71
+ + config: document includeIf conditions consistently
72
+
73
+ Doc mark-up fix.
74
+ source: <xmqqldnc4stv.fsf@gitster.g>
75
+
76
+
77
+* jc/longer-disambiguation-fix (2025-08-14) 1 commit
78
+ (merged to 'next' on 2025-09-12 at 4dddaa05fc)
79
+ + abbrev: allow extending beyond 32 chars to disambiguate
80
+
81
+ "git rev-parse --short" and friends failed to disambiguate two
82
+ objects with object names that share common prefix longer than 32
83
+ characters, which has been fixed.
84
+ source: <xmqqh5ya6iua.fsf_-_@gitster.g>
85
+
86
+
87
+* jk/curl-global-trace-components (2025-08-27) 1 commit
88
+ (merged to 'next' on 2025-09-12 at 37a826f245)
89
+ + curl: add support for curl_global_trace() components
90
+
91
+ Adjust to the way newer versions of cURL selectivel enables tracing
92
+ options, so that our tests can continue to work.
93
+ source: <20250827080702.GA3572995@coredump.intra.peff.net>
94
+
95
+
96
+* kh/doc-fast-import-markup-fix (2025-09-08) 1 commit
97
+ (merged to 'next' on 2025-09-12 at d56e1334b9)
98
+ + doc: fast-import: replace literal block with paragraph
99
+
100
+ Doc mark-up fix.
101
+ source: <09aaad696895c18c6d4dda7d6a2f4b77f84f39ba.1757363213.git.code@khaugsbakk.name>
102
+
103
+
104
+* kn/clang-format-bitfields (2025-08-26) 1 commit
105
+ (merged to 'next' on 2025-09-12 at 62dd6102f6)
106
+ + Documentation: note styling for bit fields
107
+
108
+ CodingGuidelines now spells out how bitfields are to be written.
109
+ source: <20250826121928.22317-1-karthik.188@gmail.com>
110
+
111
+
112
+* ne/alloc-free-and-null (2025-09-04) 1 commit
113
+ (merged to 'next' on 2025-09-12 at 005f763f97)
114
+ + alloc: fix dangling pointer in alloc_state cleanup
115
+
116
+ The clear_alloc_state() API function was not fully clearing the
117
+ structure for reuse, but since nobody reuses it, replace it with a
118
+ variant that frees the structure as well, making the callers simpler.
119
+ source: <pull.2040.v5.git.git.1757007856062.gitgitgadget@gmail.com>
120
+
121
+
122
+* pc/range-diff-memory-limit (2025-08-29) 1 commit
123
+ (merged to 'next' on 2025-09-12 at 022fe71829)
124
+ + range-diff: add configurable memory limit for cost matrix
125
+
126
+ "git range-diff" learned a way to limit the memory consumed by
127
+ O(N*N) cost matrix.
128
+ source: <pull.1958.v4.git.1756483374980.gitgitgadget@gmail.com>
129
+
130
+
131
+* pw/3.0-commentchar-auto-deprecation (2025-08-26) 4 commits
132
+ (merged to 'next' on 2025-09-12 at e6a855d738)
133
+ + commit: print advice when core.commentString=auto
134
+ + config: warn on core.commentString=auto
135
+ + breaking-changes: deprecate support for core.commentString=auto
136
+ + Merge branch 'ps/config-wo-the-repository' into pw/3.0-commentchar-auto-deprecation
137
+
138
+ "core.commentChar=auto" that attempts to dynamically pick a
139
+ suitable comment character is non-workable, as it is too much
140
+ trouble to support for little benefit, and is marked as deprecated.
141
+ source: <cover.1756215326.git.phillip.wood@dunelm.org.uk>
142
+
143
+
144
+* sg/line-log-boundary-fixes (2025-08-18) 2 commits
145
+ (merged to 'next' on 2025-09-12 at 0d34d3872c)
146
+ + line-log: show all line ranges touched by the same diff range
147
+ + line-log: fix assertion error
148
+
149
+ A corner case bug in "git log -L..." has been corrected.
150
+ source: <20250818111310.1283932-1-szeder.dev@gmail.com>
151
+
152
--------------------------------------------------
153
[New Topics]
154
155
+* kn/reftable-consistency-checks (2025-09-18) 9 commits
156
+ - fixup! reftable: check for trailing newline in 'tables.list'
157
+ - refs/reftable: add fsck check for checking the table name
158
+ - reftable: add code to facilitate consistency checks
159
+ - fsck: order 'fsck_msg_type' alphabetically
160
+ - Documentation/fsck-msgids: remove duplicate msg id
161
+ - reftable: ensure tables in a stack use sequential update indices
162
+ - reftable: check for trailing newline in 'tables.list'
163
+ - refs: move consistency check msg to generic layer
164
+ - refs: remove unused headers
165
+
166
+ The reftable backend learned to sanity check its on-disk data more
167
+ carefully.
168
+
169
+ Comments?
170
+ source: <20250918-228-reftable-introduce-consistency-checks-v3-0-271af03eb34d@gmail.com>
171
+
172
+
173
+* pw/rebase-i-cleanup-fix (2025-09-18) 2 commits
174
+ - sequencer: remove VERBATIM_MSG flag
175
+ - rebase -i: respect commit.cleanup when picking fixups
176
+
177
+ "git rebase -i" failed to clean-up the commit log message when the
178
+ command commits the final one in a chain of "fixup" commands, which
179
+ has been corrected.
180
+
181
+ Will merge to 'next'.
182
+ source: <cover.1758186038.git.phillip.wood@dunelm.org.uk>
183
+
184
+
185
+* tc/last-modified-recursive-fix (2025-09-18) 1 commit
186
+ - last-modified: fix bug when some paths remain unhandled
187
+
188
+ "git last-modified" operating in non-recursive mode used to trigger
189
+ a BUG(), which has been corrected.
190
+
191
+ Will merge to 'next'?
192
+ source: <20250918-toon-fix-last-modified-v3-1-0c3910e224f6@iotcl.com>
193
+
194
+
195
+* en/rust-wip (2025-09-16) 18 commits
196
+ - misc::varint: reimplement as test balloon for Rust
197
+ - misc: use BuildHelper
198
+ - build: new crate, misc
199
+ - varint: use explicit width for integers
200
+ - build-helper: cbindgen, let crates generate a header file
201
+ - build-helper: link against libgit.a and any other required C libraries
202
+ - build: new crate, build-helper
203
+ - github workflows: upload Cargo.lock
204
+ - win+Meson: do allow linking with the Rust-built xdiff
205
+ - github workflows: install rust
206
+ - help: report on whether or not Rust is enabled
207
+ - build: introduce rust
208
+ - BreakingChanges: announce Rust becoming mandatory
209
+ - doc: add a policy for using Rust
210
+ - make: merge reftable lib into libgit.a
211
+ - make: merge xdiff lib into libgit.a
212
+ - make: add -fPIE flag
213
+ - cleanup: rename variables that collide with Rust primitive type names
214
+
215
+ Expecting a reroll.
216
+ source: <pull.2043.v2.git.git.1758071798.gitgitgadget@gmail.com>
217
+
218
+
219
+* bc/sha1-256-interop-01 (2025-09-19) 10 commits
220
+ - fixup! docs: add documentation for loose objects
221
+ - t: add a prerequisite for a compatibility hash
222
+ - Allow specifying compatibility hash
223
+ - fsck: consider gpgsig headers expected in tags
224
+ - rev-parse: allow printing compatibility hash
225
+ - docs: add documentation for loose objects
226
+ - docs: improve ambiguous areas of pack format documentation
227
+ - docs: reflect actual double signature for tags
228
+ - docs: update offset order for pack index v3
229
+ - docs: update pack index v3 format
230
+
231
+ The beginning of SHA1-SHA256 interoperability work.
232
+
233
+ Comments?
234
+ source: <20250919010911.649831-1-sandals@crustytoothpaste.net>
235
+
236
+--------------------------------------------------
237
+[Stalled]
238
+
239
+These topics have been expecting updates for quite some time. I'll
240
+eject any of them when they start to conflict with other topics in
241
+'seen' and may drop them from my tree when they are dormant for too
242
+long (let's say 8 weeks is way too long, for now). After that, they
243
+can be proposed again by rerolling them in a shape that would work
244
+well with other topics in 'seen' (and of course 'next' and
245
+"master').
246
+
247
+* lc/rebase-trailer (2025-08-03) 2 commits
248
+ - rebase: support --trailer
249
+ - trailer: append trailers in-process and drop the fork to `interpret-trailers`
250
+
251
+ Expecting a reroll.
252
+ cf. <198826af571.62b85cb31711042.2415806544948206668@linux.beauty>
253
+ cf. <xmqqiki7qasu.fsf@gitster.g>
254
+ source: <20250803150059.402017-1-me@linux.beauty>
255
+
256
+
257
+* ac/deglobal-sparse-variables (2025-07-18) 3 commits
258
+ . environment: remove the global variable 'sparse_expect_files_outside_of_patterns'
259
+ . environment: move access to "core.sparsecheckoutcone" into repo_settings
260
+ . environment: move access to "core.sparsecheckout" into repo_settings
261
+
262
+ Two global variables related to sparse checkout have been moved to
263
+ the repository settings structure.
264
+
265
+ Expecting a reroll.
266
+ cf. <CAE7as+bnG6KgA8X_n36pqP15bmyM6re+xEb1MOXKvZSUdJ8Arg@mail.gmail.com>
267
+ Ejected out of 'seen' for now.
268
+ source: <cover.1752882401.git.ayu.chandekar@gmail.com>
269
+
270
+--------------------------------------------------
271
+[Cooking]
272
+
273
* pw/add-p-hunk-splitting-fix (2025-09-15) 2 commits
274
- add-patch: update hunk splitability after editing
275
- add -p: mark split hunks as undecided
@@ -103,11 +320,13 @@ Release tarballs are available at:
320
321
Will merge to 'next'?
322
source: <20250916201036.GA612463@coredump.intra.peff.net>
323
+ source: <20250916202408.GI612873@coredump.intra.peff.net>
324
325
108
-* en/xdiff-cleanup (2025-09-07) 9 commits
326
+* en/xdiff-cleanup (2025-09-19) 10 commits
327
- xdiff: treat xdfile_t.rchg like an enum
110
- - xdiff: delete chastore from xdfile_t, view with --color-words
328
+ - xdiff: delete rchg aliasing
329
+ - xdiff: delete chastore from xdfile_t
330
- xdiff: delete fields ha, line, size in xdlclass_t in favor of an xrecord_t
331
- xdiff: delete redundant array xdfile_t.ha
332
- xdiff: delete struct diffdata_t
@@ -120,9 +339,8 @@ Release tarballs are available at:
339
A lot of code clean-up of xdiff.
340
Split out of a larger topic.
341
123
- Expecting a (hopefully small and final) reroll.
124
- cf. <CABPp-BH-oaV+fJ4u50oofy54ycE5oKoYJ6O1XgEt_JfDSgXvxg@mail.gmail.com>
125
- source: <pull.2048.git.git.1757274320.gitgitgadget@gmail.com>
342
+ Comments?
343
+ source: <pull.2048.v3.git.git.1758294992.gitgitgadget@gmail.com>
344
345
346
* jc/3.0-default-initial-branch-to-main-addendum (2025-09-17) 1 commit
@@ -132,56 +350,21 @@ Release tarballs are available at:
350
Keep giving hint about the default initial branch name for users
351
who may be surprised after Git 3.0 switchover.
352
135
- Will merge to 'next'?
353
+ Will merge to 'next'.
354
source: <cover.1757518141.git.phillip.wood@dunelm.org.uk>
355
356
357
* nb/send-email-no-dup-reply-to (2025-09-16) 1 commit
140
- - send-email: don't duplicate Reply-to: in intro message
358
+ (merged to 'next' on 2025-09-18 at d7081e00ec)
359
+ + send-email: don't duplicate Reply-to: in intro message
360
361
"git send-email --compose --reply-to=<address>" used to add
362
duplicated Reply-To: header, which made mailservers unhappy. This
363
has been corrected.
364
146
- Will merge to 'next'.
365
+ Will merge to 'master'.
366
source: <175809074627.1696783.67425889158412786@noble.neil.brown.name>
367
149
---------------------------------------------------
150
-[Stalled]
151
-
152
-These topics have been expecting updates for quite some time. I'll
153
-eject any of them when they start to conflict with other topics in
154
-'seen' and may drop them from my tree when they are dormant for too
155
-long (let's say 8 weeks is way too long, for now). After that, they
156
-can be proposed again by rerolling them in a shape that would work
157
-well with other topics in 'seen' (and of course 'next' and
158
-"master').
159
-
160
-* lc/rebase-trailer (2025-08-03) 2 commits
161
- - rebase: support --trailer
162
- - trailer: append trailers in-process and drop the fork to `interpret-trailers`
163
-
164
- Expecting a reroll.
165
- cf. <198826af571.62b85cb31711042.2415806544948206668@linux.beauty>
166
- cf. <xmqqiki7qasu.fsf@gitster.g>
167
- source: <20250803150059.402017-1-me@linux.beauty>
168
-
169
-
170
-* ac/deglobal-sparse-variables (2025-07-18) 3 commits
171
- . environment: remove the global variable 'sparse_expect_files_outside_of_patterns'
172
- . environment: move access to "core.sparsecheckoutcone" into repo_settings
173
- . environment: move access to "core.sparsecheckout" into repo_settings
174
-
175
- Two global variables related to sparse checkout have been moved to
176
- the repository settings structure.
177
-
178
- Expecting a reroll.
179
- cf. <CAE7as+bnG6KgA8X_n36pqP15bmyM6re+xEb1MOXKvZSUdJ8Arg@mail.gmail.com>
180
- Ejected out of 'seen' for now.
181
- source: <cover.1752882401.git.ayu.chandekar@gmail.com>
182
-
183
---------------------------------------------------
184
-[Cooking]
368
369
* ar/submodule-gitdir-tweak (2025-09-08) 10 commits
370
- t7425: add gitdir encoding tests
@@ -221,18 +404,12 @@ well with other topics in 'seen' (and of course 'next' and
404
source: <20250908053056.956907-1-christian.couder@gmail.com>
405
406
224
-* je/doc-push (2025-09-15) 5 commits
225
- - fixup! doc: add an UPSTREAM BRANCHES section to pull/push/fetch
226
- - doc: git-push: clarify "what to push"
227
- - doc: git-push: clarify "where to push"
228
- - doc: add an UPSTREAM BRANCHES section to pull/push/fetch
229
- - doc: git-push: clarify intro
407
+* je/doc-push (2025-09-17) 2 commits
408
+ - doc: git-push: rewrite refspec specification
409
+ - doc: git-push: create PUSH RULES section
410
411
Doc updates.
232
-
233
- Expecting a reroll.
234
- cf. <70034c35-8f08-4ee0-9017-7faf6f55ae14@app.fastmail.com>
235
- source: <pull.1964.v2.git.1757703309.gitgitgadget@gmail.com>
412
+ source: <pull.1973.git.1758144815.gitgitgadget@gmail.com>
413
414
415
* rs/get-oid-with-flags-cleanup (2025-09-10) 1 commit
@@ -266,7 +443,7 @@ well with other topics in 'seen' (and of course 'next' and
443
source: <20250910-b4-pks-clar-update-v1-1-26a196237e0a@pks.im>
444
445
269
-* ps/config-get-color-fixes (2025-09-15) 5 commits
446
+* ps/config-get-color-fixes (2025-09-17) 5 commits
447
- builtin/config: do not spawn pager when printing color codes
448
- builtin/config: special-case retrieving colors without a key
449
- builtin/config: do not die in `get_color()`
@@ -278,7 +455,7 @@ well with other topics in 'seen' (and of course 'next' and
455
--type=color --default=reset no.such.thing", isn't very ergonomic.
456
457
Will merge to 'next'?
281
- source: <20250915-pks-config-color-v2-0-e4290bd8d13c@pks.im>
458
+ source: <20250918-pks-config-color-v3-0-08ea618cae26@pks.im>
459
460
461
* ps/meson-build-docs (2025-09-11) 3 commits
@@ -320,16 +497,15 @@ well with other topics in 'seen' (and of course 'next' and
497
source: <20250916182938.2193476-1-jltobler@gmail.com>
498
499
323
-* cc/fast-import-strip-signed-commits (2025-09-12) 2 commits
500
+* cc/fast-import-strip-signed-commits (2025-09-17) 2 commits
501
- fast-import: add '--signed-commits=<mode>' option
502
- gpg-interface: refactor 'enum sign_mode' parsing
503
504
"git fast-import" learned that "--signed-commits=<how>" option that
505
corresponds to that of "git fast-export".
506
330
- Expecting a (hopefully small and final) reroll.
331
- cf. <CAP8UFD3-3zjBBHP-Y9nLO-qEyhkWhD_pxFZhk6rzrC31LanDMQ@mail.gmail.com>
332
- source: <20250912124042.2523683-1-christian.couder@gmail.com>
507
+ Will merge to 'next'?
508
+ source: <20250917181427.3193500-1-christian.couder@gmail.com>
509
510
511
* pw/3.0-default-initial-branch-to-main (2025-09-10) 4 commits
@@ -342,7 +518,7 @@ well with other topics in 'seen' (and of course 'next' and
518
Declare that "git init" that is not otherwise configured uses
519
'main' as the initial branch, not 'master', starting Git 3.0.
520
345
- Will merge to 'next'?
521
+ Will merge to 'next'.
522
source: <cover.1757518141.git.phillip.wood@dunelm.org.uk>
523
524
@@ -361,45 +537,39 @@ well with other topics in 'seen' (and of course 'next' and
537
538
539
* ps/rust-balloon (2025-09-15) 9 commits
364
- - ci: enable Rust for breaking-changes jobs
365
- - ci: convert "pedantic" job into full build with breaking changes
366
- - BreakingChanges: announce Rust becoming mandatory
367
- - varint: reimplement as test balloon for Rust
368
- - varint: use explicit width for integers
369
- - help: report on whether or not Rust is enabled
370
- - Makefile: introduce infrastructure to build internal Rust library
371
- - Makefile: reorder sources after includes
372
- - meson: add infrastructure to build internal Rust library
540
+ . ci: enable Rust for breaking-changes jobs
541
+ . ci: convert "pedantic" job into full build with breaking changes
542
+ . BreakingChanges: announce Rust becoming mandatory
543
+ . varint: reimplement as test balloon for Rust
544
+ . varint: use explicit width for integers
545
+ . help: report on whether or not Rust is enabled
546
+ . Makefile: introduce infrastructure to build internal Rust library
547
+ . Makefile: reorder sources after includes
548
+ . meson: add infrastructure to build internal Rust library
549
550
Dip our toes a bit to (optionally) use Rust implemented helper
551
called from our C code.
552
377
- Will merge to 'next'?
553
+ Ejected for now, to give preference to en/*rust* topics.
554
source: <20250915-b4-pks-rust-breaking-change-v5-0-dc3a32fbb216@pks.im>
555
556
381
-* kh/doc-fast-import-markup-fix (2025-09-08) 1 commit
382
- (merged to 'next' on 2025-09-12 at d56e1334b9)
383
- + doc: fast-import: replace literal block with paragraph
384
-
385
- Doc mark-up fix.
386
-
387
- Will merge to 'master'.
388
- source: <09aaad696895c18c6d4dda7d6a2f4b77f84f39ba.1757363213.git.code@khaugsbakk.name>
389
-
390
-
391
-* ms/refs-optimize (2025-09-06) 5 commits
557
+* ms/refs-optimize (2025-09-19) 9 commits
558
- t: add test for git refs optimize subcommand
559
- t0601: refactor tests to be shareable
560
- builtin/refs: add optimize subcommand
395
- - doc: factor out common option
561
+ - doc: pack-refs: factor out common options
562
- builtin/pack-refs: factor out core logic into a shared library
563
+ - builtin/pack-refs: convert to use the generic refs_optimize() API
564
+ - reftable-backend: implement 'optimize' action
565
+ - files-backend: implement 'optimize' action
566
+ - refs: add a generic 'optimize' API
567
568
"git refs optimize" is added for not very well explained reason
569
despite it does the same thing as "git pack-refs"...
570
401
- Expecting a reroll.
402
- source: <20250906075147.1076656-1-meetsoni3017@gmail.com>
571
+ Comments?
572
+ source: <20250919082647.535213-1-meetsoni3017@gmail.com>
573
574
575
* sj/string-list (2025-09-17) 4 commits
@@ -457,16 +627,6 @@ well with other topics in 'seen' (and of course 'next' and
627
source: <20250917-587-git-fetch-1-fails-fetches-on-case-insensitive-repositories-v4-0-da3c74a08ed0@gmail.com>
628
629
460
-* ag/doc-sendmail-gmail-example-update (2025-08-26) 1 commit
461
- (merged to 'next' on 2025-09-12 at 54e0dab4b0)
462
- + docs: update sendmail docs to use more secure SMTP server for Gmail
463
-
464
- Doc update.
465
-
466
- Will merge to 'master'.
467
- source: <20250826150919.5239-1-gargaditya08@live.com>
468
-
469
-
630
* en/rust-xdiff (2025-09-07) 9 commits
631
- xdiff: change the types of dstart, dend, rchg, and rindex in xdfile_t
632
- xdiff: make xdfile_t.nreff a usize instead of long
@@ -501,76 +661,22 @@ well with other topics in 'seen' (and of course 'next' and
661
source: <pull.1962.v4.git.1757531669.gitgitgadget@gmail.com>
662
663
504
-* kn/clang-format-bitfields (2025-08-26) 1 commit
505
- (merged to 'next' on 2025-09-12 at 62dd6102f6)
506
- + Documentation: note styling for bit fields
507
-
508
- CodingGuidelines now spells out how bitfields are to be written.
509
-
510
- Will merge to 'master'.
511
- source: <20250826121928.22317-1-karthik.188@gmail.com>
512
-
513
-
514
-* jk/curl-global-trace-components (2025-08-27) 1 commit
515
- (merged to 'next' on 2025-09-12 at 37a826f245)
516
- + curl: add support for curl_global_trace() components
517
-
518
- Adjust to the way newer versions of cURL selectivel enables tracing
519
- options, so that our tests can continue to work.
520
-
521
- Will merge to 'master'.
522
- source: <20250827080702.GA3572995@coredump.intra.peff.net>
523
-
524
-
525
-* kh/you-still-use-whatchanged-fix (2025-09-14) 8 commits
526
- . BreakingChanges: remove claim about whatchanged reports
527
- . whatchanged: remove not-even-shorter clause
528
- . whatchanged: hint about git-log(1) and aliasing
529
- . you-still-use-that??: help the user help themselves
530
- . t0014: test shadowing of aliases for a sample of builtins
531
- . git: allow alias-shadowing deprecated builtins
532
- . git: move seen-alias bookkeeping into handle_alias(...)
533
- . git: add `deprecated` category to --list-cmds
664
+* kh/you-still-use-whatchanged-fix (2025-09-17) 9 commits
665
+ - BreakingChanges: remove claim about whatchanged reports
666
+ - whatchanged: remove not-even-shorter clause
667
+ - whatchanged: hint about git-log(1) and aliasing
668
+ - you-still-use-that??: help the user help themselves
669
+ - t0014: test shadowing of aliases for a sample of builtins
670
+ - git: allow alias-shadowing deprecated builtins
671
+ - git: move seen-alias bookkeeping into handle_alias(...)
672
+ - git: add `deprecated` category to --list-cmds
673
+ - Makefile: don’t add whatchanged after it has been removed
674
675
Update "do you still use it?" message given by a command that is
676
deeply deprecated and allow us to suggest alternatives.
677
538
- Breaks 'seen' built with WITH_BREAKING_CHANGES.
539
- cf. <xmqqy0qffrri.fsf@gitster.g>
540
- source: <cover.1757879060.git.code@khaugsbakk.name>
541
-
542
-
543
-* pc/range-diff-memory-limit (2025-08-29) 1 commit
544
- (merged to 'next' on 2025-09-12 at 022fe71829)
545
- + range-diff: add configurable memory limit for cost matrix
546
-
547
- "git range-diff" learned a way to limit the memory consumed by
548
- O(N*N) cost matrix.
549
-
550
- Will merge to 'master'.
551
- source: <pull.1958.v4.git.1756483374980.gitgitgadget@gmail.com>
552
-
553
-
554
-* ne/alloc-free-and-null (2025-09-04) 1 commit
555
- (merged to 'next' on 2025-09-12 at 005f763f97)
556
- + alloc: fix dangling pointer in alloc_state cleanup
557
-
558
- The clear_alloc_state() API function was not fully clearing the
559
- structure for reuse, but since nobody reuses it, replace it with a
560
- variant that frees the structure as well, making the callers simpler.
561
-
562
- Will merge to 'master'.
563
- source: <pull.2040.v5.git.git.1757007856062.gitgitgadget@gmail.com>
564
-
565
-
566
-* jc/doc-includeif-hasconfig-remote-url-fix (2025-08-21) 1 commit
567
- (merged to 'next' on 2025-09-12 at 3b91910cbd)
568
- + config: document includeIf conditions consistently
569
-
570
- Doc mark-up fix.
571
-
572
- Will merge to 'master'.
573
- source: <xmqqldnc4stv.fsf@gitster.g>
678
+ Will merge to 'next'?
679
+ source: <cover.1758139856.short.code@khaugsbakk.name>
680
681
682
* jk/add-i-color (2025-09-08) 4 commits
@@ -589,41 +695,6 @@ well with other topics in 'seen' (and of course 'next' and
695
source: <20250908164157.GA1323487@coredump.intra.peff.net>
696
697
592
-* sg/line-log-boundary-fixes (2025-08-18) 2 commits
593
- (merged to 'next' on 2025-09-12 at 0d34d3872c)
594
- + line-log: show all line ranges touched by the same diff range
595
- + line-log: fix assertion error
596
-
597
- Fix for a corner case bug in "git log -L...".
598
-
599
- Will merge to 'master'.
600
- source: <20250818111310.1283932-1-szeder.dev@gmail.com>
601
-
602
-
603
-* jc/longer-disambiguation-fix (2025-08-14) 1 commit
604
- (merged to 'next' on 2025-09-12 at 4dddaa05fc)
605
- + abbrev: allow extending beyond 32 chars to disambiguate
606
-
607
- "git rev-parse --short" and friends failed to disambiguate two
608
- objects with object names that share common prefix longer than 32
609
- characters.
610
-
611
- Will merge to 'master'.
612
- source: <xmqqh5ya6iua.fsf_-_@gitster.g>
613
-
614
-
615
-* ag/send-email-imap-sent (2025-08-11) 2 commits
616
- (merged to 'next' on 2025-09-12 at bb82691e0a)
617
- + send-email: enable copying emails to an IMAP folder without actually sending them
618
- + send-email: add ability to send a copy of sent emails to an IMAP folder
619
-
620
- "git send-email" learned to drive "git imap-send" to store already
621
- sent e-mails in an IMAP folder.
622
-
623
- Will merge to 'master'.
624
- source: <PN3PR01MB9597E8E33868386C997D2563B82BA@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM>
625
-
626
-
698
* ds/sparse-checkout-clean (2025-09-12) 7 commits
699
- t: expand tests around sparse merges and clean
700
- sparse-index: point users to new 'clean' action
@@ -639,18 +710,3 @@ well with other topics in 'seen' (and of course 'next' and
710
711
Will merge to 'next'?
712
source: <pull.1941.v3.git.1757673011.gitgitgadget@gmail.com>
642
-
643
-
644
-* pw/3.0-commentchar-auto-deprecation (2025-08-26) 4 commits
645
- (merged to 'next' on 2025-09-12 at e6a855d738)
646
- + commit: print advice when core.commentString=auto
647
- + config: warn on core.commentString=auto
648
- + breaking-changes: deprecate support for core.commentString=auto
649
- + Merge branch 'ps/config-wo-the-repository' into pw/3.0-commentchar-auto-deprecation
650
-
651
- Proposes to deprecate "core.commentChar=auto" that attempts to
652
- dynamically pick a suitable comment character, as it is too much
653
- trouble to support for little benefit.
654
-
655
- Will merge to 'master'.
656
- source: <cover.1756215326.git.phillip.wood@dunelm.org.uk>