What's cooking (2025/09 #01)
Junio C Hamano committed
Sep 2, 2025 at 08:34 UTC
0bfa84918ce2327b987c5661a52debebf5331b0c
1 file changed
+27
-147
whats-cooking.txt
+27
-147
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Aug 2025, #12; Fri, 29)
2
+Subject: What's cooking in git.git (Sep 2025, #01; Tue, 2)
3
X-master-at: 6ad802182101d622e6a4132f48292ddfa79e2024
4
-X-next-at: 3baa7cb742e267e07c93c00c15fa04107b8e9fab
4
+X-next-at: 4c02a37b29ea955e35380eada24af394d7169ebf
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Aug 2025, #12; Fri, 29)
7
+What's cooking in git.git (Sep 2025, #01; Tue, 2)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -46,132 +46,7 @@ Release tarballs are available at:
46
https://www.kernel.org/pub/software/scm/git/
47
48
--------------------------------------------------
49
-[Graduated to 'master']
50
-
51
-* ad/t1517-short-help-tests-fix (2025-08-19) 1 commit
52
- (merged to 'next' on 2025-08-21 at f686ad352a)
53
- + t/t1517: mark tests that fail with GIT_TEST_INSTALLED
54
-
55
- Test fix.
56
- source: <20250819074631.3303-1-adam@dinwoodie.org>
57
-
58
-
59
-* bc/doc-compat-object-format-not-working (2025-08-25) 1 commit
60
- (merged to 'next' on 2025-08-26 at 5224444f11)
61
- + docs: note that extensions.compatobjectformat is incomplete
62
-
63
- The compatObjectFormat extension is used to hide an incomplete
64
- feature that is not yet usable for any purpose other than
65
- developing the feature further. Document it as such to discourage
66
- its use by mere mortals.
67
- source: <20250825221101.611876-1-sandals@crustytoothpaste.net>
68
-
69
-
70
-* ds/doc-community-discord (2025-08-20) 1 commit
71
- (merged to 'next' on 2025-08-21 at 7f9aa8da4e)
72
- + doc: add discord to ways of getting help
73
-
74
- Discord has been added to the first contribution documentation as
75
- another way to ask for help.
76
- source: <pull.2033.v3.git.git.1755679018997.gitgitgadget@gmail.com>
77
-
78
-
79
-* je/doc-rebase (2025-08-22) 5 commits
80
- (merged to 'next' on 2025-08-26 at 0d9a1d75d5)
81
- + doc: git-rebase: update discussion of internals
82
- + doc: git-rebase: move --onto explanation down
83
- + doc: git rebase: clarify arguments syntax
84
- + doc: git rebase: dedup merge conflict discussion
85
- + doc: git-rebase: start with an example
86
-
87
- Documentation for "git rebase" has been updated.
88
- source: <pull.1949.v9.git.1755909782.gitgitgadget@gmail.com>
89
-
90
-
91
-* jk/describe-blob (2025-08-18) 5 commits
92
- (merged to 'next' on 2025-08-21 at 671998ff24)
93
- + describe: pass commit to describe_commit()
94
- + describe: handle blob traversal with no commits
95
- + describe: catch unborn branch in describe_blob()
96
- + describe: error if blob not found
97
- + describe: pass oid struct by const pointer
98
-
99
- "git describe <blob>" misbehaves and/or crashes in some corner
100
- cases, which has been taught to exit with failure gracefully.
101
- source: <20250818205812.GA1018043@coredump.intra.peff.net>
102
-
103
-
104
-* jk/fetch-check-graph-objects-fix (2025-08-23) 1 commit
105
- (merged to 'next' on 2025-08-26 at 51a561116f)
106
- + fetch-pack: re-scan when double-checking graph objects
107
-
108
- Under a race against another process that is repacking the
109
- repository, especially a partially cloned one, "git fetch" may
110
- mistakenly think some objects we do have are missing, which has
111
- been corrected.
112
- source: <20250824050040.GA228050@coredump.intra.peff.net>
113
-
114
-
115
-* jk/no-clobber-dangling-symref-with-fetch (2025-08-19) 4 commits
116
- (merged to 'next' on 2025-08-21 at 29b96663c0)
117
- + refs: do not clobber dangling symrefs
118
- + t5510: prefer "git -C" to subshell for followRemoteHEAD tests
119
- + t5510: stop changing top-level working directory
120
- + t5510: make confusing config cleanup more explicit
121
-
122
- "git fetch" can clobber a symref that is dangling when the
123
- remote-tracking HEAD is set to auto update, which has been
124
- corrected.
125
- source: <20250819192004.GA1058857@coredump.intra.peff.net>
126
-
127
-
128
-* js/doc-gitk-history (2025-08-19) 1 commit
129
- (merged to 'next' on 2025-08-21 at e7e1a08f82)
130
- + doc/gitk: update reference to the external project
131
-
132
- Manual page for "gitk" is updated with the current maintainer's
133
- name.
134
- source: <249056e7-1332-4e6f-8d07-16c80fd4913e@kdbg.org>
135
-
136
-
137
-* js/progress-delay-fix (2025-08-25) 1 commit
138
- (merged to 'next' on 2025-08-26 at 4e832eb295)
139
- + progress: pay attention to (customized) delay time
140
-
141
- The start_delayed_progress() function in the progress eye-candy API
142
- did not clear its internal state, making an initial delay value
143
- larger than 1 second ineffective, which has been corrected.
144
- source: <7b848623-ce64-4679-9b5e-9d91d947b269@kdbg.org>
145
-
146
-
147
-* ps/reftable-libgit2-cleanup (2025-08-12) 8 commits
148
- (merged to 'next' on 2025-08-21 at ff82e3fa11)
149
- + refs/reftable: always reload stacks when creating lock
150
- + reftable: don't second-guess errors from flock interface
151
- + reftable/stack: handle outdated stacks when compacting
152
- + reftable/stack: allow passing flags to `reftable_stack_add()`
153
- + reftable/stack: fix compiler warning due to missing braces
154
- + reftable/stack: reorder code to avoid forward declarations
155
- + reftable/writer: drop Git-specific `QSORT()` macro
156
- + reftable/writer: fix type used for number of records
157
-
158
- Code clean-ups.
159
- source: <20250812-pks-reftable-fixes-for-libgit2-v3-0-cf3b2267867e@pks.im>
160
-
161
-
162
-* sg/line-log-merge-optim (2025-08-24) 4 commits
163
- (merged to 'next' on 2025-08-26 at e110ef974a)
164
- + line-log: simplify condition checking for merge commits
165
- + line-log: initialize diff queue in process_ranges_ordinary_commit()
166
- + line-log: get rid of the parents array in process_ranges_merge_commit()
167
- + line-log: avoid unnecessary tree diffs when processing merge commits
168
-
169
- "git log -L..." compared trees of multiple parents with the tree of the
170
- merge result in an unnecessarily inefficient way.
171
- source: <20250824190644.2573279-1-szeder.dev@gmail.com>
172
-
173
---------------------------------------------------
174
-[New Topics]
49
+[Cooking]
50
51
* ag/doc-sendmail-gmail-example-update (2025-08-26) 1 commit
52
- docs: update sendmail docs to use more secure SMTP server for Gmail
@@ -183,12 +58,13 @@ Release tarballs are available at:
58
59
60
* da/cargo-serialize (2025-08-26) 1 commit
186
- - Makefile: build libgit-rs and libgit-sys serially
61
+ (merged to 'next' on 2025-08-29 at 5a193b1525)
62
+ + Makefile: build libgit-rs and libgit-sys serially
63
64
Makefile tried to run multiple "cargo build" which would not work
65
very well; serialize their execution to work it around.
66
191
- Will merge to 'next'.
67
+ Will merge to 'master'.
68
source: <20250826233525.2635432-1-davvid@gmail.com>
69
70
@@ -250,14 +126,15 @@ Release tarballs are available at:
126
127
128
* ds/ls-files-lazy-unsparse (2025-08-15) 1 commit
253
- - ls-files: conditionally leave index sparse
129
+ (merged to 'next' on 2025-08-29 at a48fee2dde)
130
+ + ls-files: conditionally leave index sparse
131
132
"git ls-files <pathspec>..." should not necessarily have to expand
133
the index fully if a sparsified directory is excluded by the
134
pathspec; the code is taught to expand the index on demand to avoid
135
this.
136
260
- Will merge to 'next'.
137
+ Will merge to 'master'.
138
source: <pull.1955.git.1755274373717.gitgitgadget@gmail.com>
139
140
@@ -281,8 +158,6 @@ Release tarballs are available at:
158
Will merge to 'next'?
159
source: <pull.2040.v3.git.git.1756472406487.gitgitgadget@gmail.com>
160
284
---------------------------------------------------
285
-[Cooking]
161
162
* ds/doc-ggg-pr-fork-clarify (2025-08-23) 1 commit
163
(merged to 'next' on 2025-08-25 at 71aea64ee4)
@@ -412,25 +287,28 @@ Release tarballs are available at:
287
source: <20250816213642.3517822-1-adrian.ratiu@collabora.com>
288
289
415
-* je/doc-add (2025-08-19) 2 commits
290
+* je/doc-add (2025-08-29) 3 commits
291
+ - doc: rephrase the purpose of the staging area
292
(merged to 'next' on 2025-08-25 at 0c84501ed2)
293
+ doc: git-add: simplify discussion of ignored files
294
+ doc: git-add: clarify intro & add an example
295
296
Documentation for "git add" has been updated.
297
422
- Will merge to 'master'.
298
+ Will merge to 'next' and then to 'master'.
299
source: <pull.1952.v3.git.1755636370.gitgitgadget@gmail.com>
300
+ source: <pull.1952.v4.git.1756468502.gitgitgadget@gmail.com>
301
302
303
* ds/path-walk-repack-fix (2025-08-25) 2 commits
427
- - path-walk: create initializer for path lists
428
- - path-walk: fix setup of pending objects
304
+ (merged to 'next' on 2025-08-29 at 13028ffb8e)
305
+ + path-walk: create initializer for path lists
306
+ + path-walk: fix setup of pending objects
307
308
"git repack --path-walk" lost objects in some corner cases, which
309
has been corrected.
310
433
- Will merge to 'next'.
311
+ Will merge to 'master'.
312
cf. <CABPp-BHFxxGrqKc0m==TjQNjDGdO=H5Rf6EFsf2nfE1=TuraOQ@mail.gmail.com>
313
source: <pull.1956.v2.git.1756126197.gitgitgadget@gmail.com>
314
@@ -510,14 +388,15 @@ Release tarballs are available at:
388
389
390
* am/xdiff-hash-tweak (2025-07-28) 2 commits
513
- - xdiff: optimize xdl_hash_record_verbatim
514
- - xdiff: refactor xdl_hash_record()
391
+ (merged to 'next' on 2025-08-29 at 43590f0b38)
392
+ + xdiff: optimize xdl_hash_record_verbatim
393
+ + xdiff: refactor xdl_hash_record()
394
395
Inspired by Ezekiel's recent effort to showcase Rust interface, the
396
hash function implementation used to hash lines have been updated
397
to the one used for ELF symbol lookup by Glibc.
398
520
- Will merge to 'next'.
399
+ Will merge to 'master'.
400
cf. <xmqqecsvqal6.fsf@gitster.g>
401
source: <20250728190520.10962-1-amonakov@ispras.ru>
402
@@ -570,14 +449,15 @@ Release tarballs are available at:
449
450
451
* tc/last-modified (2025-08-05) 3 commits
573
- - last-modified: use Bloom filters when available
574
- - t/perf: add last-modified perf script
575
- - last-modified: new subcommand to show when files were last modified
452
+ (merged to 'next' on 2025-08-29 at 3f3e111189)
453
+ + last-modified: use Bloom filters when available
454
+ + t/perf: add last-modified perf script
455
+ + last-modified: new subcommand to show when files were last modified
456
457
A new command "git last-modified" is proposed to show the closest
458
ancestor commit that touched each path.
459
580
- Will merge to 'next'.
460
+ Will merge to 'master'.
461
source: <20250730175510.987383-1-toon@iotcl.com>
462
463