What's cooking (2024/10 #05)
Junio C Hamano committed
Oct 8, 2024 at 23:29 UTC
0ee567925e8b4deabcebc1f72a6bc5e763420c7f
1 file changed
+192
-40
whats-cooking.txt
+192
-40
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Oct 2024, #04; Sun, 6)
2
+Subject: What's cooking in git.git (Oct 2024, #05; Tue, 8)
3
X-master-at: 777489f9e09c8d0dd6b12f9d90de6376330577a2
4
X-next-at: 4ca455297942c5c9616351bc68bad2034c719206
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Oct 2024, #04; Sun, 6)
7
+What's cooking in git.git (Oct 2024, #05; Tue, 8)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -17,7 +17,9 @@ 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
-Git 2.47 (final) has been tagged.
20
+Git 2.47 (final) has been tagged, and the 'maint' branch now points
21
+at v2.47.0. Let's hope we didn't introduce too many regressions
22
+this time.
23
24
Copies of the source code to Git live in many repositories, and the
25
following is a list of the ones I push into or their mirrors. Some
@@ -47,6 +49,156 @@ Release tarballs are available at:
49
50
https://www.kernel.org/pub/software/scm/git/
51
52
+--------------------------------------------------
53
+[New Topics]
54
+
55
+* cw/worktree-relative (2024-10-08) 4 commits
56
+ - worktree: add test for path handling in linked worktrees
57
+ - worktree: link worktrees with relative paths
58
+ - worktree: refactor infer_backlink() to use *strbuf
59
+ - Merge branch 'es/worktree-repair-copied' into cw/worktrees-relative
60
+ (this branch uses es/worktree-repair-copied.)
61
+
62
+ An extra worktree attached to a repository points at each other to
63
+ allow finding the repository from the worktree and vice versa
64
+ possible. Turn this linkage to relative paths.
65
+
66
+ Will merge to 'next'?
67
+ source: <20241007-wt_relative_paths-v3-0-622cf18c45eb@pm.me>
68
+
69
+
70
+* ds/path-walk (2024-10-08) 17 commits
71
+ - pack-objects: thread the path-based compression
72
+ - pack-objects: refactor path-walk delta phase
73
+ - scalar: enable path-walk during push via config
74
+ - pack-objects: enable --path-walk via config
75
+ - repack: update usage to match docs
76
+ - repack: add --path-walk option
77
+ - pack-objects: introduce GIT_TEST_PACK_PATH_WALK
78
+ - p5313: add performance tests for --path-walk
79
+ - pack-objects: update usage to match docs
80
+ - pack-objects: add --path-walk option
81
+ - pack-objects: extract should_attempt_deltas()
82
+ - path-walk: add prune_all_uninteresting option
83
+ - revision: create mark_trees_uninteresting_dense()
84
+ - path-walk: allow visiting tags
85
+ - path-walk: allow consumer to specify object types
86
+ - t6601: add helper for testing path-walk API
87
+ - path-walk: introduce an object walk by path
88
+
89
+ source: <pull.1813.git.1728396723.gitgitgadget@gmail.com>
90
+
91
+
92
+* hy/partial-repack-fix (2024-10-08) 3 commits
93
+ . partial-clone: update doc
94
+ . t0410: adapt tests to repack changes
95
+ . repack: pack everything into packfile
96
+
97
+ "git repack" avoids losing local objects that are reachable from
98
+ objects in a packfile fetched from a promisor remote.
99
+
100
+ Comments?
101
+ Breaks CI.
102
+ cf. <xmqqzfnexlku.fsf@gitster.g>
103
+ source: <20241008081350.8950-1-hanyang.tony@bytedance.com>
104
+
105
+
106
+* jh/config-unset-doc-fix (2024-10-08) 1 commit
107
+ - git-config.1: remove value from positional args in unset usage
108
+
109
+ Docfix.
110
+
111
+ Will merge to 'next'.
112
+ source: <20241008142920.570244-2-joshiheinrichs@gmail.com>
113
+
114
+
115
+* jk/fsmonitor-event-listener-race-fix (2024-10-08) 2 commits
116
+ - fsmonitor: initialize fs event listener before accepting clients
117
+ - simple-ipc: split async server initialization and running
118
+
119
+ On macOS, fsmonitor can fall into a race condition that results in
120
+ a client waiting forever to be notified for an event that have
121
+ already happened. This problem has been corrected.
122
+
123
+ Will merge to 'next'.
124
+ source: <20241008083121.GA676391@coredump.intra.peff.net>
125
+
126
+
127
+* js/doc-platform-support-link-fix (2024-10-07) 1 commit
128
+ - docs: fix the `maintain-git` links in `technical/platform-support`
129
+
130
+ Docfix.
131
+
132
+ Will merge to 'next'.
133
+ source: <pull.1812.git.1728337764963.gitgitgadget@gmail.com>
134
+
135
+
136
+* kh/merge-tree-doc (2024-10-08) 2 commits
137
+ - doc: merge-tree: use || directly
138
+ - doc: merge-tree: provide a commit message
139
+
140
+ Docfix.
141
+
142
+ Comments?
143
+ source: <cover.1728413450.git.code@khaugsbakk.name>
144
+
145
+
146
+* pb/clar-build-fix (2024-10-07) 1 commit
147
+ - Makefile: fix dependency for $(UNIT_TEST_DIR)/clar/clar.o
148
+
149
+ Build fix.
150
+
151
+ Will merge to 'next'.
152
+ source: <pull.1810.git.1728323033680.gitgitgadget@gmail.com>
153
+
154
+
155
+* ps/cache-tree-w-broken-index-entry (2024-10-07) 3 commits
156
+ - unpack-trees: detect mismatching number of cache-tree/index entries
157
+ - cache-tree: detect mismatching number of index entries
158
+ - cache-tree: refactor verification to return error codes
159
+
160
+ Fail gracefully instead of crashing when attempting to write the
161
+ contents of a corrupt in-core index as a tree object.
162
+
163
+ Comments?
164
+ source: <cover.1728275640.git.ps@pks.im>
165
+
166
+
167
+* ps/maintenance-start-crash-fix (2024-10-08) 1 commit
168
+ - builtin/gc: fix crash when running `git maintenance start`
169
+
170
+ "git maintenance start" crashed due to an uninitialized variable
171
+ reference, which has been corrected.
172
+
173
+ Will merge to 'next'.
174
+ Brown paper bag fix.
175
+ source: <976c97081af7c62960bd71d1b70039657e7cb711.1728389731.git.ps@pks.im>
176
+
177
+
178
+* ua/t3404-cleanup (2024-10-07) 2 commits
179
+ - t3404: employing test_line_count() to replace test
180
+ - t3404: avoid losing exit status with focus on `git show` and `git cat-file`
181
+
182
+ Test update.
183
+
184
+ Will merge to 'next'?
185
+ source: <pull.1805.v6.git.git.1728299466.gitgitgadget@gmail.com>
186
+
187
+
188
+* xx/remote-server-option-config (2024-10-08) 5 commits
189
+ - ls-remote: leakfix for not clearing server_options
190
+ - fetch: respect --server-option when fetching multiple remotes
191
+ - transport.c::handshake: make use of server options from remote
192
+ - remote: introduce remote.<name>.serverOption configuration
193
+ - transport: introduce parse_transport_option() method
194
+
195
+ A new configuration variable remote.<name>.serverOption makes the
196
+ transport layer act as if the --serverOption=<value> option is
197
+ given from the command line.
198
+
199
+ Will merge to 'next'.
200
+ source: <pull.1776.v3.git.git.1728358699.gitgitgadget@gmail.com>
201
+
202
--------------------------------------------------
203
[Cooking]
204
@@ -88,16 +240,6 @@ Release tarballs are available at:
240
source: <pull.1806.v2.git.1727956724.gitgitgadget@gmail.com>
241
242
91
-* kn/fsmonitor-event-listener-fix (2024-10-02) 1 commit
92
- - fsmonitor: fix hangs by delayed fs event listening
93
-
94
- Under high load, fsmonitor process can hang at start-up, which has
95
- been corrected.
96
-
97
- Comments?
98
- source: <pull.1804.git.1727862424713.gitgitgadget@gmail.com>
99
-
100
-
243
* jc/a-commands-without-the-repo (2024-10-06) 3 commits
244
- archive: remove the_repository global variable
245
- annotate: remove usage of the_repository global
@@ -174,6 +316,7 @@ Release tarballs are available at:
316
317
* es/worktree-repair-copied (2024-09-23) 1 commit
318
- worktree: repair copied repository and linked worktrees
319
+ (this branch is used by cw/worktree-relative.)
320
321
The heuristics in "git worktree repair" can be confused when a
322
worktree and its repository are copied and break correctly
@@ -273,26 +416,6 @@ Release tarballs are available at:
416
source: <20240910163000.1985723-1-christian.couder@gmail.com>
417
418
276
-* ds/pack-name-hash-tweak (2024-10-04) 6 commits
277
- - test-tool: add helper for name-hash values
278
- - p5313: add size comparison test
279
- - git-repack: update usage to match docs
280
- - pack-objects: add GIT_TEST_FULL_NAME_HASH
281
- - repack: test --full-name-hash option
282
- - pack-objects: add --full-name-hash option
283
-
284
- In a repository with too many (more than --window size) similarly
285
- named files, "git repack" would not find good delta-base candidate
286
- and worse, it may not use a blob from exactly the same path as a
287
- good delta-base candidate. Optionally replace the name hash so
288
- that only blobs at the same path and nothing else are used as
289
- delta-base candidate.
290
-
291
- On hold.
292
- cf. <34346998-deac-4e1f-9d5f-218f664e9e08@gmail.com>
293
- source: <pull.1785.v2.git.1726692381.gitgitgadget@gmail.com>
294
-
295
-
419
* sj/ref-contents-check (2024-09-30) 9 commits
420
- ref: add symlink ref content check for files backend
421
- t0602: add ref content checks for worktrees
@@ -340,20 +463,18 @@ Release tarballs are available at:
463
source: <ZwBsbW5jsFw0mxKk@nand.local>
464
465
343
-* js/libgit-rust (2024-09-09) 7 commits
344
- . SQUASH???
466
+* js/libgit-rust (2024-10-08) 5 commits
467
. Makefile: add option to build and test libgit-rs and libgit-rs-sys
468
. libgit: add higher-level libgit crate
347
- . config: add git_configset_alloc() and git_configset_clear_and_free()
348
- . libgit-sys: add repo initialization and config access
469
+ . libgit-sys: also export some config_set functions
470
. libgit-sys: introduce Rust wrapper for libgit.a
471
. common-main: split init and exit code into new files
472
473
An rust binding to libgit.a functions has been introduced.
474
354
- Expecting a reroll.
355
- cf. <xmqqv7z8tjd7.fsf@gitster.g>
356
- source: <20240906221853.257984-1-calvinwan@google.com>
475
+ Needs review.
476
+ Seems to get dependencies wrong.
477
+ source: <cover.1728429158.git.steadmon@google.com>
478
479
480
* jc/too-many-arguments (2024-08-06) 4 commits
@@ -409,3 +530,34 @@ Release tarballs are available at:
530
531
Has been expecting a reroll for too long.
532
source: <20240824172028.39419-1-shyamthakkar001@gmail.com>
533
+
534
+
535
+* kn/fsmonitor-event-listener-fix (2024-10-02) 1 commit
536
+ . fsmonitor: fix hangs by delayed fs event listening
537
+
538
+ Under high load, fsmonitor process can hang at start-up, which has
539
+ been corrected.
540
+
541
+ Superseded by the jk/fsmonitor-event-listener-race-fix topic
542
+ cf. <CAOTNsDyxmRZ155vV-Jh=1obMnR+F4ExY9B136fiGk0Vd23-zrw@mail.gmail.com>
543
+ source: <pull.1804.git.1727862424713.gitgitgadget@gmail.com>
544
+
545
+
546
+* ds/pack-name-hash-tweak (2024-10-04) 6 commits
547
+ . test-tool: add helper for name-hash values
548
+ . p5313: add size comparison test
549
+ . git-repack: update usage to match docs
550
+ . pack-objects: add GIT_TEST_FULL_NAME_HASH
551
+ . repack: test --full-name-hash option
552
+ . pack-objects: add --full-name-hash option
553
+
554
+ In a repository with too many (more than --window size) similarly
555
+ named files, "git repack" would not find good delta-base candidate
556
+ and worse, it may not use a blob from exactly the same path as a
557
+ good delta-base candidate. Optionally replace the name hash so
558
+ that only blobs at the same path and nothing else are used as
559
+ delta-base candidate.
560
+
561
+ Retracted.
562
+ cf. <f89ba1ef-4cd4-4963-8de0-0323216246aa@gmail.com>
563
+ source: <pull.1785.v2.git.1726692381.gitgitgadget@gmail.com>