What's cooking (2025/08 #08)
Junio C Hamano committed
Aug 18, 2025 at 08:52 UTC
b7ebef0b22fb9e4b21f35315753e271a159ee9fb
1 file changed
+9
-6
whats-cooking.txt
+9
-6
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Aug 2025, #07; Sun, 17)
3
-X-master-at: e5ab6b3e5a3f0a94a429526e0fe6f491955ac053
4
-X-next-at: 8c5e2ae05d41c0752c436e7e1fc78ff5fcd3ab81
2
+Subject: What's cooking in git.git (Aug 2025, #08; Mon, 18)
3
+X-master-at: c44beea485f0f2feaf460e2ac87fdd5608d63cf0
4
+X-next-at: 7ce5a0a67ee2fce1fa86eaa2cdf5d7d51f7185c7
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Aug 2025, #07; Sun, 17)
7
+What's cooking in git.git (Aug 2025, #08; Mon, 18)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -17,6 +17,10 @@ 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.51 has been tagged. Let's see if there is any unexpected
21
+fallout for the rest of this week, and then start merging down what
22
+has been cooking in 'next' (and rewind 'next' while doing so).
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
26
repositories have only a subset of branches.
@@ -409,8 +413,7 @@ Release tarballs are available at:
413
source: <20250801220423.1230969-1-gitster@pobox.com>
414
415
412
-* am/xdiff-hash-tweak (2025-07-28) 3 commits
413
- - fixup! xdiff: optimize xdl_hash_record_verbatim
416
+* am/xdiff-hash-tweak (2025-07-28) 2 commits
417
- xdiff: optimize xdl_hash_record_verbatim
418
- xdiff: refactor xdl_hash_record()
419