What's cooking (2026/04 #06)

diff --git a/whats-cooking.txt b/whats-cooking.txt
index 1d7d34b6edea0c1983d7df1d4fed051c1a64fd9e..2aa003c505434a0cb6844d80768f60c28767daae 100644 (file)
--- a/whats-cooking.txt
+++ b/whats-cooking.txt
@@ -1,10 +1,10 @@
 To: git@vger.kernel.org
-Subject: What's cooking in git.git (Apr 2026, #05)
-X-master-at: e8955061076952cc5eab0300424fc48b601fe12d
-X-next-at: c7ae2d5bb8f97b06f1b31df2f2456646924c8be7
+Subject: What's cooking in git.git (Apr 2026, #06)
+X-master-at: 94f057755b7941b321fd11fec1b2e3ca5313a4e0
+X-next-at: f703ff30bc5e33a20cacd2b6ec9f4b2e71eee37e
 Bcc: lwn@lwn.net, gitster@pobox.com
 
-What's cooking in git.git (Apr 2026, #05)
+What's cooking in git.git (Apr 2026, #06)
 -----------------------------------------
 
 Here are the topics that have been cooking in my tree.  Commits
@@ -17,6 +17,14 @@ A topic without enough support may be discarded after a long period
 of no activity (of course they can be resubmitted when new interests
 arise).
 
+Git 2.54 (final) has been tagged.  Thank you, everybody, for
+participating.  I will go offline for a couple of weeks starting
+this evening, hopefully after updating 'next' and possibly also
+pushing out the first batch of the new cycle.  There is no
+designated interim maintainer this time, but I trust that the
+community can self organize if the shape of the release and the tree
+turns out to be super bad ;-).
+
 Copies of the source code to Git live in many repositories, and the
 following is a list of the ones I push into or their mirrors.  Some
 repositories have only a subset of branches.
@@ -46,18 +54,7 @@ Release tarballs are available at:
        https://www.kernel.org/pub/software/scm/git/
 
 --------------------------------------------------
-[Graduated to 'master']
-
-* jk/midx-write-v1-by-default (2026-04-16) 1 commit
-  (merged to 'next' on 2026-04-16 at 1b296b0f55)
- + MIDX: revert the default version to v1
-
- As writing version 2 MIDX files by default breaks older versions of
- Git and its reimplementations, use V2 only when necessary.
- source: <20260416200659.GB1887222@coredump.intra.peff.net>
-
---------------------------------------------------
-[New Topics]
+[Cooking]
 
 * sb/userdiff-lisp-family (2026-04-14) 2 commits
  - userdiff: extend Scheme support to cover other Lisp dialects
@@ -77,7 +74,8 @@ Release tarballs are available at:
 
  Test clean-up.
 
- Will merge to 'next'?
+ Expecting a (hopefully trivial) reroll?
+ cf. <aeXTcZ7K9a6kUIbk@pks.im>
  source: <20260414141828.27576-1-r.siddharth.shrimali@gmail.com>
 
 
@@ -141,7 +139,7 @@ Release tarballs are available at:
  source: <pull.2087.git.1776331259.gitgitgadget@gmail.com>
 
 
-* en/batch-prefetch (2026-04-16) 3 commits
+* en/batch-prefetch (2026-04-17) 3 commits
  - grep: prefetch necessary blobs
  - builtin/log: prefetch necessary blobs for `git cherry`
  - patch-ids.h: add missing trailing parenthesis in documentation comment
@@ -152,7 +150,7 @@ Release tarballs are available at:
  reasonable performance.
 
  Needs review.
- source: <pull.2089.git.1776379694.gitgitgadget@gmail.com>
+ source: <pull.2089.v2.git.1776472347.gitgitgadget@gmail.com>
 
 
 * en/diffstat-utf8-truncation-fix (2026-04-17) 1 commit
@@ -163,11 +161,9 @@ Release tarballs are available at:
  into account error cases (e.g., an invalid UTF-8 sequence, or a
  control character).
 
- Needs review.
- source: <pull.2093.git.1776443163041.gitgitgadget@gmail.com>
+ Will merge to 'next' and then to 'master'?
+ source: <pull.2093.v2.git.1776465910538.gitgitgadget@gmail.com>
 
---------------------------------------------------
-[Cooking]
 
 * sp/refs-reduce-the-repository (2026-04-04) 3 commits
   (merged to 'next' on 2026-04-09 at bb1d626802)
@@ -238,7 +234,8 @@ Release tarballs are available at:
  updated to work correctly when 'set -e' is in effect, which helps
  detect misspelled test commands.
 
- Will merge to 'next'?
+ Expecting a (hopefully final) reroll.
+ cf. <aeXTcZ7K9a6kUIbk@pks.im>
  source: <20260417-b4-pks-tests-with-set-e-v4-0-44d43efdafb1@pks.im>
 
 
@@ -318,18 +315,6 @@ Release tarballs are available at:
  source: <20260403100135.3901610-1-joerg@thalheim.io>
 
 
-* sp/refs-with-less-the-repository (2026-04-04) 3 commits
- - refs/reftable-backend: drop uses of the_repository
- - refs: remove the_hash_algo global state
- - refs: add struct repository parameter in get_files_ref_lock_timeout_ms()
-
- Reduce the reference to the_repository in the refs subsystem.
-
- Will merge to 'next'.
- cf. <adYV6NK93Kzg1EYG@pks.im>
- source: <20260404135914.61195-1-shreyanshpaliwalcmsmn@gmail.com>
-
-
 * dl/cache-tree-fully-valid-fix (2026-04-06) 1 commit
   (merged to 'next' on 2026-04-13 at 68c82a9f37)
  + cache-tree: fix inverted object existence check in cache_tree_fully_valid
@@ -355,8 +340,7 @@ Release tarballs are available at:
  source: <pull.2077.git.1775322767.gitgitgadget@gmail.com>
 
 
-* lp/repack-propagate-promisor-debugging-info (2026-04-10) 7 commits
- - SQUASH???
+* lp/repack-propagate-promisor-debugging-info (2026-04-18) 6 commits
  - repack-promisor: add missing headers
  - t7703: test for promisor file content after geometric repack
  - t7700: test for promisor file content after repack
@@ -369,9 +353,8 @@ Release tarballs are available at:
  repack" has been taught to carry this information forward to
  packfiles that are newly created.
 
- Expecting a (hopefully small and final) reroll.
- cf. <adpVMfHowCBY75I1@lorenzo-VM>
- source: <cover.1775861047.git.lorenzo.pegorari2002@gmail.com>
+ Comments?
+ source: <cover.1776384902.git.lorenzo.pegorari2002@gmail.com>
 
 
 * th/promisor-quiet-per-repo (2026-04-06) 1 commit
@@ -398,7 +381,7 @@ Release tarballs are available at:
  ODB transaction interface is being reworked to explicitly handle
  object writes.
 
- Comments?
+ Will merge to 'next'?
  source: <20260402213220.2651523-1-jltobler@gmail.com>