What's cooking (2022/04 #05)
Junio C Hamano committed
Apr 18, 2022 at 01:23 UTC
490c8148aa21a3e820bfb058efc26831a4806d94
1 file changed
+40
-44
whats-cooking.txt
+40
-44
@@ -1,24 +1,26 @@
1
To: git@vger.kernel.org
2
Bcc: lwn@lwn.net
3
-Subject: What's cooking in git.git (Apr 2022, #04; Thu, 14)
4
-X-master-at: 4027e30c5395c9c1aeea85e99f51ac62f5148145
5
-X-next-at: 8af0fa9b8e9e4d9f3a9661b1fd1f8c8822364ea5
3
+Subject: What's cooking in git.git (Apr 2022, #05; Mon, 18)
4
+X-master-at: 6cd33dceed60949e2dbc32e3f0f5e67c4c882e1e
5
+X-next-at: b9c8b46e9451eb1f82393119d53aa151b6f7ff83
6
7
-What's cooking in git.git (Apr 2022, #04; Thu, 14)
7
+What's cooking in git.git (Apr 2022, #05; Mon, 18)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
11
prefixed with '+' are in 'next' (being in 'next' is a sign that a
12
topic is stable enough to be used and are candidate to be in a
13
future release). Commits prefixed with '-' are only in 'seen',
14
-which means nothing more than that I have found them of interest for
15
-some reason (like "it may have hard-to-resolve conflicts with
16
-another topic already in flight" or "this may turn out to be
17
-useful"). Do not read too much into a topic being in (or not in)
18
-'seen'. The ones marked with '.' do not appear in any of the
19
-integration branches, but I am still holding onto them.
20
-
21
-Copies of the source code to Git live in many repositories, and the
14
+and aren't considered "accepted" at all.
15
+
16
+Git 2.36 has been tagged. As usual, we'll keep the tree closed for
17
+a few days for anything other than brown-paper-bag bugfixes (if
18
+needed) and then by the end of the week hopefully we can start
19
+sifting what is in 'next' to those to graduate to 'master' and those
20
+to be kicked back to 'seen'. We'll start taking new topics probably
21
+next week at the earliest.
22
+
23
+cCopies of the source code to Git live in many repositories, and the
24
following is a list of the ones I push into or their mirrors. Some
25
repositories have only a subset of branches.
26
@@ -49,39 +51,25 @@ Release tarballs are available at:
51
--------------------------------------------------
52
[Graduated to 'master']
53
52
-* jc/relnotes-updates (2022-04-13) 2 commits
53
- (merged to 'next' on 2022-04-14 at a19d9a5cc2)
54
- + RelNotes: mention safe.directory
55
- + RelNotes: clarify "bisect run unexecutable" tweak
56
-
57
- Wording updates for 2.36 release notes.
54
+* cb/buggy-gcc-12-workaround (2022-04-15) 2 commits
55
+ (merged to 'next' on 2022-04-15 at 48e68dd0fd)
56
+ + config.mak.dev: alternative workaround to gcc 12 warning in http.c
57
+ + config.mak.dev: workaround gcc 12 bug affecting "pedantic" CI job
58
59
-* jc/revert-ref-transaction-hook-changes (2022-04-13) 3 commits
60
- (merged to 'next' on 2022-04-14 at 94ac0baec8)
61
- + RelNotes: revert the description on the reverted topics
62
- + Revert "fetch: increase test coverage of fetches"
63
- + Revert "Merge branch 'ps/avoid-unnecessary-hook-invocation-with-packed-refs'"
64
-
65
- Revert the "deletion of a ref should not trigger transaction events
66
- for loose and packed ref backends separately" that regresses the
67
- behaviour when a ref is not modified since it was packed.
59
+ A couple of work around for CI breaking warnings from gcc 12.
60
+ source: <20220415231342.35980-1-carenas@gmail.com>
61
62
--------------------------------------------------
63
[New Topics]
64
72
-* sa/t1011-use-helpers (2022-04-12) 1 commit
73
- - t1011: replace test -f with test_path_is_file
74
-
75
- A GSoC practice.
76
-
77
- Will merge to 'next'.
78
- source: <20220412203722.10484-1-siddharthasthana31@gmail.com>
65
+* cm/reftable-0-length-memset (2022-04-15) 1 commit
66
+ - reftable: avoid undefined behaviour breaking t0032
67
68
+ Code clean-up.
69
81
-* ep/coverage-report-wants-test-to-have-run (2022-04-13) 1 commit
82
- - Makefile: add a prerequisite to the coverage-report target
70
+ Will merge to 'next'?
71
+ source: <20220415083058.29495-1-carenas@gmail.com>
72
84
- source: <20220414022513.31465-1-gitter.spiros@gmail.com>
73
74
--------------------------------------------------
75
[Stalled]
@@ -138,6 +126,21 @@ Release tarballs are available at:
126
--------------------------------------------------
127
[Cooking]
128
129
+* sa/t1011-use-helpers (2022-04-12) 1 commit
130
+ - t1011: replace test -f with test_path_is_file
131
+
132
+ A GSoC practice.
133
+
134
+ Will merge to 'next'.
135
+ source: <20220412203722.10484-1-siddharthasthana31@gmail.com>
136
+
137
+
138
+* ep/coverage-report-wants-test-to-have-run (2022-04-13) 1 commit
139
+ - Makefile: add a prerequisite to the coverage-report target
140
+
141
+ source: <20220414022513.31465-1-gitter.spiros@gmail.com>
142
+
143
+
144
* pw/test-malloc-with-sanitize-address (2022-04-11) 1 commit
145
- tests: make SANITIZE=address imply TEST_NO_MALLOC_CHECK
146
@@ -507,13 +510,6 @@ Release tarballs are available at:
510
source: <20220217225408.GB7@edef91d97c94>
511
512
510
-* ab/http-gcc-12-workaround (2022-03-25) 1 commit
511
- - http API: fix dangling pointer issue noted by GCC 12.0
512
-
513
- Work around false warning pre-release of GCC 12.
514
- source: <patch-v3-1.1-69190804c67-20220325T143322Z-avarab@gmail.com>
515
-
516
-
513
* tk/simple-autosetupmerge (2022-02-25) 2 commits
514
- t3200: tests for new branch.autosetupmerge option "simple"
515
- merge: new autosetupmerge option 'simple' for matching branches