What's cooking (2024/11 #05)
Junio C Hamano committed
Nov 11, 2024 at 17:26 UTC
61ada19650594d19fcab8e7e88e90766ca3abcf2
1 file changed
+50
-76
whats-cooking.txt
+50
-76
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Nov 2024, #04; Fri, 8)
3
-X-master-at: facbe4f633e4ad31e641f64617bc88074c659959
4
-X-next-at: 60cca158198dd42396c273ab7a273339f8157e86
2
+Subject: What's cooking in git.git (Nov 2024, #05; Mon, 11)
3
+X-master-at: b31fb630c0fc6869a33ed717163e8a1210460d94
4
+X-next-at: c49de5d5d93ad88a5b8f1f2a66f44d11acfc90ac
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Nov 2024, #04; Fri, 8)
7
+What's cooking in git.git (Nov 2024, #05; Mon, 11)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -17,9 +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
-It has been a bit longer than usual since the last issue of the
21
-"What's cooking report". We still have way too many topics that are
22
-not sufficiently reviewed. Help is greatly appreciated.
20
+A few commits to update git-gui are in. There are still too many
21
+topics that are left unreviewed, and the 'next' branch is not
22
+gaining topics as quickly as it usually would.
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
@@ -50,61 +50,39 @@ Release tarballs are available at:
50
https://www.kernel.org/pub/software/scm/git/
51
52
--------------------------------------------------
53
-[Graduated to 'master']
54
-
55
-* cw/config-extensions (2024-10-22) 1 commit
56
- (merged to 'next' on 2024-10-30 at 875fa0b619)
57
- + doc: consolidate extensions in git-config documentation
58
- (this branch is used by cw/worktree-extension.)
59
-
60
- Centralize documentation for repository extensions into a single place.
61
- source: <20241021-cleanup-extension-docs-v1-1-ab02cece3132@pm.me>
62
-
63
-
64
-* jk/left-right-bitmap (2024-11-01) 1 commit
65
- (merged to 'next' on 2024-11-01 at f1d0c395f5)
66
- + rev-list: skip bitmap traversal for --left-right
67
-
68
- When called with '--left-right' and '--use-bitmap-index', 'rev-list'
69
- will produce output without any left/right markers, which has been
70
- corrected.
71
- source: <20241101121606.GA2327410@coredump.intra.peff.net>
72
-
73
-
74
-* kn/arbitrary-suffixes (2024-10-24) 1 commit
75
- (merged to 'next' on 2024-10-30 at 3eedf30c6c)
76
- + CodingGuidelines: discourage arbitrary suffixes in function names
53
+[New Topics]
54
78
- Update the project's CodingGuidelines to discourage naming functions
79
- with a "_1()" suffix.
80
- source: <20241024105357.2605168-1-karthik.188@gmail.com>
55
+* ps/ref-backend-migration-optim (2024-11-08) 10 commits
56
+ - reftable/block: optimize allocations by using scratch buffer
57
+ - reftable/block: rename `block_writer::buf` variable
58
+ - reftable/writer: optimize allocations by using a scratch buffer
59
+ - refs: don't normalize log messages with `REF_SKIP_CREATE_REFLOG`
60
+ - refs: skip collision checks in initial transactions
61
+ - refs: use "initial" transaction semantics to migrate refs
62
+ - refs/files: support symbolic and root refs in initial transaction
63
+ - refs: introduce "initial" transaction flag
64
+ - refs/files: move logic to commit initial transaction
65
+ - refs: allow passing flags when setting up a transaction
66
67
+ Optimize migration procedure between two ref backends.
68
83
-* kn/ci-clang-format-tidy (2024-10-18) 2 commits
84
- (merged to 'next' on 2024-10-30 at d063e828d5)
85
- + clang-format: align consecutive macro definitions
86
- + clang-format: re-adjust line break penalties
69
+ Needs review.
70
+ source: <20241108-pks-refs-optimize-migrations-v1-0-7fd37fa80e35@pks.im>
71
88
- Updates the '.clang-format' to match project conventions.
89
- source: <cover.1729241030.git.karthik.188@gmail.com>
72
73
+* js/log-remerge-keep-ancestry (2024-11-11) 1 commit
74
+ - log: --remerge-diff needs to keep around commit parents
75
92
-* ps/upgrade-clar (2024-10-21) 5 commits
93
- (merged to 'next' on 2024-10-30 at b8b092bb78)
94
- + cmake: set up proper dependencies for generated clar headers
95
- + cmake: fix compilation of clar-based unit tests
96
- + Makefile: extract script to generate clar declarations
97
- + Makefile: adjust sed command for generating "clar-decls.h"
98
- + t/unit-tests: update clar to 206accb
99
- (this branch is used by ps/build.)
76
+ "git log -p --remerge-diff --reverse" was completely broken.
77
101
- Buildfix and upgrade of Clar to a newer version.
102
- source: <cover.1729506329.git.ps@pks.im>
78
+ Comments?
79
+ cf. <CABPp-BHauuserYU8t5ybn+ghqRb-c85qwwjLWVe-e5EC8sVVxQ@mail.gmail.com>
80
+ source: <pull.1825.git.1731073435641.gitgitgadget@gmail.com>
81
82
--------------------------------------------------
105
-[New Topics]
83
+[Cooking]
84
107
-* ps/reftable-iterator-reuse (2024-11-05) 9 commits
85
+* ps/reftable-iterator-reuse (2024-11-08) 9 commits
86
- refs/reftable: reuse iterators when reading refs
87
- reftable/merged: drain priority queue on reseek
88
- reftable/stack: add mechanism to notify callers on reload
@@ -113,7 +91,7 @@ Release tarballs are available at:
91
- refs/reftable: read references via `struct reftable_backend`
92
- refs/reftable: handle reloading stacks in the reftable backend
93
- refs/reftable: encapsulate reftable stack
116
- - Merge branch 'ps/reftable-detach' into HEAD
94
+ - Merge branch 'ps/reftable-detach' into ps/reftable-iterator-reuse
95
(this branch uses ps/reftable-detach.)
96
97
Optimize reading random references out of the reftable backend by
@@ -148,15 +126,16 @@ Release tarballs are available at:
126
source: <20241106192236.GC880133@coredump.intra.peff.net>
127
128
151
-* js/range-diff-diff-merges (2024-11-08) 1 commit
129
+* js/range-diff-diff-merges (2024-11-11) 1 commit
130
- range-diff: optionally include merge commits' diffs in the analysis
131
132
"git range-diff" learned to optionally show and compare merge
133
commits in the ranges being compared, with the --diff-merges
134
option.
135
158
- Waiting for response to reviews.
159
- source: <pull.1734.git.1731000007391.gitgitgadget@gmail.com>
136
+ Almost there.
137
+ cf. <CABPp-BHNVEvYx4KwmiSQhPqidhPffb5hGBt=uT5NKqBPXC4j0w@mail.gmail.com>
138
+ source: <pull.1734.v2.git.1731073383564.gitgitgadget@gmail.com>
139
140
141
* ps/leakfixes-part-10 (2024-11-07) 27 commits
@@ -194,8 +173,6 @@ Release tarballs are available at:
173
Needs review.
174
source: <cover.1730901926.git.ps@pks.im>
175
197
---------------------------------------------------
198
-[Cooking]
176
177
* ak/t1016-style (2024-11-03) 1 commit
178
(merged to 'next' on 2024-11-05 at ee100e90d3)
@@ -265,7 +242,7 @@ Release tarballs are available at:
242
source: <cover.1730491845.git.jonathantanmy@google.com>
243
244
268
-* ds/path-walk-1 (2024-10-31) 6 commits
245
+* ds/path-walk-1 (2024-11-11) 6 commits
246
- path-walk: mark trees and blobs as UNINTERESTING
247
- path-walk: visit tags and cached objects
248
- path-walk: allow consumer to specify object types
@@ -276,9 +253,8 @@ Release tarballs are available at:
253
Introduce a new API to visit objects in batches based on a common
254
path, or by type.
255
279
- Under discussion.
280
- cf. <ZyUqr/wb5K4Og9j9@nand.local>
281
- source: <pull.1818.git.1730356023.gitgitgadget@gmail.com>
256
+ Comments?
257
+ source: <pull.1818.v2.git.1731181272.gitgitgadget@gmail.com>
258
259
260
* bc/ancient-ci (2024-11-01) 3 commits
@@ -323,15 +299,14 @@ Release tarballs are available at:
299
source: <cover.1730979849.git.code@khaugsbakk.name>
300
301
326
-* as/show-index-uninitialized-hash (2024-11-04) 2 commits
302
+* as/show-index-uninitialized-hash (2024-11-11) 2 commits
303
- t5300: add test for 'show-index --object-format'
304
- show-index: fix uninitialized hash function
305
306
Regression fix for 'show-index' when run outside of a repository.
307
332
- Expecting a reroll.
333
- cf. <xmqq4j4mv5o6.fsf@gitster.g>
334
- source: <20241104192958.64310-1-abhijeet.nkt@gmail.com>
308
+ Comments?
309
+ source: <20241109092739.14276-1-abhijeet.nkt@gmail.com>
310
311
312
* ps/mingw-rename (2024-11-06) 3 commits
@@ -349,7 +324,7 @@ Release tarballs are available at:
324
source: <cover.1730042775.git.ps@pks.im>
325
326
352
-* ps/reftable-detach (2024-10-23) 8 commits
327
+* ps/reftable-detach (2024-11-08) 8 commits
328
- reftable/system: provide thin wrapper for lockfile subsystem
329
- reftable/stack: drop only use of `get_locked_file_path()`
330
- reftable/system: provide thin wrapper for tempfile subsystem
@@ -364,7 +339,7 @@ Release tarballs are available at:
339
using fewer pieces of Git's infrastructure.
340
341
Needs review.
367
- source: <cover.1729677003.git.ps@pks.im>
342
+ source: <cover.1731047193.git.ps@pks.im>
343
344
345
* km/config-remote-by-name (2024-10-21) 1 commit
@@ -506,19 +481,19 @@ Release tarballs are available at:
481
source: <cover.1729771605.git.ps@pks.im>
482
483
509
-* ej/cat-file-remote-object-info (2024-10-31) 6 commits
484
+* ej/cat-file-remote-object-info (2024-11-11) 6 commits
485
- cat-file: add remote-object-info to batch-command
511
- - cat-file: add declaration of variable i inside its for loop
486
- transport: add client support for object-info
487
- serve: advertise object-info feature
488
- fetch-pack: move fetch initialization
489
- fetch-pack: refactor packet writing
490
+ - cat-file: add declaration of variable i inside its for loop
491
492
"git cat-file --batch" and friends can optionally ask a remote
493
server about objects it does not have.
494
495
Needs review.
521
- source: <20241028203457.19715-1-eric.peijian@gmail.com>
496
+ source: <20241108162441.50736-1-eric.peijian@gmail.com>
497
498
499
* cc/promisor-remote-capability (2024-09-10) 4 commits
@@ -538,14 +513,14 @@ Release tarballs are available at:
513
source: <20240910163000.1985723-1-christian.couder@gmail.com>
514
515
541
-* sj/ref-contents-check (2024-10-21) 9 commits
516
+* sj/ref-contents-check (2024-11-11) 9 commits
517
- ref: add symlink ref content check for files backend
518
- ref: check whether the target of the symref is a ref
519
- ref: add basic symref content check for files backend
520
- ref: add more strict checks for regular refs
521
- ref: port git-fsck(1) regular refs check for files backend
522
- ref: support multiple worktrees check for refs
548
- - ref: initialize target name outside of check functions
523
+ - ref: initialize ref name outside of check functions
524
- ref: check the full refname instead of basename
525
- ref: initialize "fsck_ref_report" with zero
526
@@ -554,9 +529,8 @@ Release tarballs are available at:
529
wouldn't have written itself (e.g., missing terminating end-of-line
530
after the full object name).
531
557
- Needs review.
558
- cf. <ZxZ+xteOnm0im5vC@nand.local>
559
- source: <ZxZX5HDdq_R0C77b@ArchLinux>
532
+ Comments?
533
+ source: <ZzCiCGxL4Adnd_eq@ArchLinux>
534
535
536
* js/libgit-rust (2024-10-16) 5 commits