Meta/cook: shorten title of what's cooking reports
Also force US/Pacific timezone, so that "1 calendar week" can consistently be computed (of course 'cal' needs to be run with the same timezone).
Junio C Hamano committed
Dec 11, 2025 at 18:28 UTC
ea7d60c0b59d9c533c5191d1c12ddc6c9e0885d9
2 files changed
+51
-68
cook
+8
-6
@@ -3,6 +3,8 @@
3
4
my $MASTER = 'master'; # for now
5
6
+$::ENV{TZ} = "US/Pacific"; # for now
7
+
8
use strict;
9
10
my %reverts = ('next' => {
@@ -419,13 +421,13 @@ EOF
421
422
$text = <<EOF;
423
To: git\@vger.kernel.org
422
-Subject: What's cooking in git.git ($mon $year, #$issue; $dow, $date)
424
+Subject: What's cooking in git.git ($mon $year, #$issue)
425
X-$MASTER-at: $master_at
426
X-next-at: $next_at
427
Bcc: lwn\@lwn.net, gitster\@pobox.com
428
427
-What's cooking in git.git ($mon $year, #$issue; $dow, $date)
428
---------------------------------------------------
429
+What's cooking in git.git ($mon $year, #$issue)
430
+-----------------------------------------
431
432
$text
433
EOF
@@ -434,12 +436,12 @@ EOF
436
}
437
438
my $blurb_match = <<'EOF';
437
-(?:(?i:\s*[a-z]+: .*|\s.*)\n)*Subject: What's cooking in \S+ \((\w+) (\d+), #(\d+); (\w+), (\d+)\)
439
+(?:(?i:\s*[a-z]+: .*|\s.*)\n)*Subject: What's cooking in \S+ \((\w+) (\d+), #(\d+)(?:; (\w+), (\d+))?\)
440
X-[a-z]*-at: ([0-9a-f]{40})
441
X-next-at: ([0-9a-f]{40})(?:\n(?i:\s*[a-z]+: .*|\s.*))*
442
441
-What's cooking in \S+ \(\1 \2, #\3; \4, \5\)
442
--{30,}
443
+What's cooking in \S+ \(\1 \2, #\3(?:;[^)]*)?\)
444
+-{20,}
445
\n*
446
EOF
447
whats-cooking.txt
+43
-62
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Dec 2025, #02)
2
+Subject: What's cooking in git.git (Dec 2025, #03)
3
X-master-at: e85ae279b0d58edc2f4c3fd5ac391b51e1223985
4
-X-next-at: 3fc767764aec198db34053b394419bf8a1e8e5d2
4
+X-next-at: 674ac2bdf7c6f0d156df6d082f5137cb019b8bec
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Dec 2025, #02)
7
+What's cooking in git.git (Dec 2025, #03)
8
-----------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -17,9 +17,6 @@ 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
-The maintainer will only be online for a few days during the first
21
-week of December, so please expect things to be slower in my tree.
22
-
20
Copies of the source code to Git live in many repositories, and the
21
following is a list of the ones I push into or their mirrors. Some
22
repositories have only a subset of branches.
@@ -49,54 +46,32 @@ Release tarballs are available at:
46
https://www.kernel.org/pub/software/scm/git/
47
48
--------------------------------------------------
52
-[Graduated to 'master']
53
-
54
-* bc/zsh-testsuite (2025-11-27) 2 commits
55
- (merged to 'next' on 2025-11-30 at b4a3081f6f)
56
- + t5564: fix test hang under zsh's sh mode
57
- + t0614: use numerical comparison with test_line_count
58
-
59
- A few tests have been updated to work under the shell compatible
60
- mode of zsh.
61
- source: <20251128012107.101431-1-sandals@crustytoothpaste.net>
62
-
63
-
64
-* en/replay-doc-revision-range (2025-11-28) 1 commit
65
- (merged to 'next' on 2025-11-30 at 37ba09bea2)
66
- + Documentation/git-replay.adoc: fix errors around revision range
67
-
68
- The use of "revision" (a connected set of commits) has been
69
- clarified in the "git replay" documentation.
70
- source: <pull.2012.git.1764391464952.gitgitgadget@gmail.com>
71
-
72
-
73
-* pw/replay-exclude-gpgsig-fix (2025-11-26) 1 commit
74
- (merged to 'next' on 2025-11-30 at 3dda1242db)
75
- + replay: do not copy "gpgsign-sha256" header
76
- (this branch is used by ps/history and pw/replay-drop-empty.)
77
-
78
- "git replay" forgot to omit the "gpgsig-sha256" extended header
79
- from the resulting commit the same way it omits "gpgsig", which has
80
- been corrected.
81
- source: <4f04af5790353b074cf122c450c1cd3f8d1cecf3.1764167611.git.phillip.wood@dunelm.org.uk>
49
+[New Topics]
50
51
+* jt/repo-struct-more-objinfo (2025-12-09) 6 commits
52
+ - builtin/repo: add object disk size info to structure table
53
+ - builtin/repo: add disk size info to keyvalue stucture output
54
+ - builtin/repo: add inflated object info to structure table
55
+ - builtin/repo: add inflated object info to keyvalue structure output
56
+ - builtin/repo: humanise count values in structure output
57
+ - builtin/repo: group per-type object values into struct
58
84
-* yc/xdiff-patience-optim (2025-11-26) 1 commit
85
- (merged to 'next' on 2025-11-30 at db62d67599)
86
- + xdiff: optimize patience diff's LCS search
59
+ More object database related information are shown in "git repo
60
+ structure" output.
61
88
- The way patience diff finds LCS has been optimized.
89
- source: <pull.2109.v2.git.git.1764209766305.gitgitgadget@gmail.com>
62
+ Comments?
63
+ source: <20251209225820.2861276-1-jltobler@gmail.com>
64
65
--------------------------------------------------
92
-[New Topics]
66
+[Cooking]
67
68
* jc/capability-leak (2025-12-06) 1 commit
95
- - connect: plug protocol capability leak
69
+ (merged to 'next' on 2025-12-10 at cfe8ce92b1)
70
+ + connect: plug protocol capability leak
71
72
Leakfix.
73
99
- Will merge to 'next'.
74
+ Will merge to 'master'.
75
source: <xmqqfr9mnbu9.fsf@gitster.g>
76
77
@@ -107,48 +82,54 @@ Release tarballs are available at:
82
83
"git replay" documentation updates.
84
110
- Will merge to 'next'.
85
+ Expecting a (hopefully small and final) reroll.
86
+ cf. <39b57721-ab9e-489d-a382-16d9fe94c300@app.fastmail.com>
87
source: <CV_replay_conflict.101@msgid.xyz>
88
89
114
-* lo/repo-info-keys (2025-12-07) 1 commit
90
+* lo/repo-info-keys (2025-12-09) 3 commits
91
- repo: add new flag --keys to git-repo-info
92
+ - repo: add a default output format to enum output_format
93
+ - Merge branch 'lo/repo-struct-z' into lo/repo-info-keys
94
(this branch uses lo/repo-struct-z.)
95
96
"git repo info" learns "--keys" action to list known keys.
97
120
- Expecting a reroll.
121
- source: <20251204210843.79411-1-lucasseikioshiro@gmail.com>
98
+ Comments?
99
+ source: <20251209194616.61620-1-lucasseikioshiro@gmail.com>
100
101
102
* kh/doc-pre-commit-fix (2025-12-07) 1 commit
125
- - doc: join default pre-commit paragraphs
103
+ (merged to 'next' on 2025-12-10 at f21f000140)
104
+ + doc: join default pre-commit paragraphs
105
106
Docfix.
107
129
- Will merge to 'next'.
108
+ Will merge to 'master'.
109
source: <pre-commit_when_enabled.10a@msgid.xyz>
110
111
112
* kh/doc-send-email-paragraph-fix (2025-12-08) 1 commit
134
- - doc: send-email: fix broken list continuation
113
+ (merged to 'next' on 2025-12-10 at 674ac2bdf7)
114
+ + doc: send-email: fix broken list continuation
115
116
Docfix.
117
138
- Will merge to 'next'.
118
+ Will merge to 'master'.
119
source: <send-email_list_contin.112@msgid.xyz>
120
121
122
* mh/doc-config-gui-gcwarning (2025-12-08) 1 commit
143
- - config: document 'gui.GCWarning'
123
+ (merged to 'next' on 2025-12-10 at 15d6df9a04)
124
+ + config: document 'gui.GCWarning'
125
126
Docfix.
127
147
- Will merge to 'next'.
128
+ Will merge to 'master'.
129
source: <20251208190400.64920-1-matthewhughes934@gmail.com>
130
131
151
-* ps/odb-alternates-object-sources (2025-12-08) 8 commits
132
+* ps/odb-alternates-object-sources (2025-12-10) 8 commits
133
- odb: write alternates via sources
134
- odb: read alternates via sources
135
- odb: drop forward declaration of `read_info_alternates()`
@@ -160,12 +141,13 @@ Release tarballs are available at:
141
142
Code refactoring around alternate object store.
143
163
- Comments?
164
- source: <20251208-b4-pks-odb-alternates-via-source-v1-0-e7ebb8b18c03@pks.im>
144
+ Will merge to 'next'.
145
+ source: <20251210-b4-pks-odb-alternates-via-source-v2-0-eb336815f9ab@pks.im>
146
147
167
-* ps/repack-avoid-noop-midx-rewrite (2025-12-08) 2 commits
168
- - builtin/repack: don't regenerate MIDX unless needed
148
+* ps/repack-avoid-noop-midx-rewrite (2025-12-10) 3 commits
149
+ - midx-write: skip rewriting MIDX with `--stdin-packs` unless needed
150
+ - midx-write: extract function to test whether MIDX needs updating
151
- midx: fix `BUG()` when getting preferred pack without a reverse index
152
153
Even when there is no changes in the packfile and no need to
@@ -173,7 +155,7 @@ Release tarballs are available at:
155
file, which has been corrected.
156
157
Comments?
176
- source: <20251208-pks-skip-noop-rewrite-v1-0-430d52dba9f0@pks.im>
158
+ source: <20251210-pks-skip-noop-rewrite-v2-0-f813a9e44f28@pks.im>
159
160
161
* sb/doc-update-ref-markup-fix (2025-12-08) 1 commit
@@ -184,8 +166,6 @@ Release tarballs are available at:
166
Will merget to 'next'.
167
source: <pull.2123.git.git.1765261419802.gitgitgadget@gmail.com>
168
187
---------------------------------------------------
188
-[Cooking]
169
170
* ap/packfile-promisor-object-optim (2025-12-08) 2 commits
171
- packfile: skip hash checks in add_promisor_object()
@@ -353,6 +333,7 @@ Release tarballs are available at:
333
* tc/last-modified-active-paths-optimization (2025-11-28) 1 commit
334
(merged to 'next' on 2025-12-05 at 42c18b607f)
335
+ last-modified: fix use of uninitialized memory
336
+ (this branch is used by tc/memzero-array.)
337
338
Recent optimization to "last-modified" command introduced use of
339
uninitialized block of memory, which has been corrected.