What's cooking (2022/02 #04)
Junio C Hamano committed
Feb 15, 2022 at 09:24 UTC
318da73d1dd9d83c3d3ddf4e3ead59443047e80e
1 file changed
+73
-132
whats-cooking.txt
+73
-132
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
Bcc: lwn@lwn.net
3
-Subject: What's cooking in git.git (Feb 2022, #03; Sat, 12)
3
+Subject: What's cooking in git.git (Feb 2022, #04; Tue, 15)
4
X-master-at: b80121027d1247a0754b3cc46897fee75c050b44
5
-X-next-at: 83b2b277ed60276e529455a66ea1f50a6e513b26
5
+X-next-at: 7e23e61f3f2abdae506f09b247827f12a86031cf
6
7
-What's cooking in git.git (Feb 2022, #03; Sat, 12)
7
+What's cooking in git.git (Feb 2022, #04; Tue, 15)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -18,8 +18,6 @@ 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
-The third batch of topics have been merged.
22
-
21
Many new topics have sketchy or even empty topic description in the
22
list below; help to fill them in is very much appreciated ;-)
23
@@ -52,98 +50,72 @@ Release tarballs are available at:
50
https://www.kernel.org/pub/software/scm/git/
51
52
--------------------------------------------------
55
-[Graduated to 'master']
56
-
57
-* ab/no-errno-from-resolve-ref-unsafe (2022-01-26) 2 commits
58
- (merged to 'next' on 2022-02-04 at d98254efe0)
59
- + refs API: remove "failure_errno" from refs_resolve_ref_unsafe()
60
- + sequencer: don't use die_errno() on refs_resolve_ref_unsafe() failure
61
-
62
- Remaining code-clean-up.
63
- source: <cover-v4-0.2-00000000000-20220126T143427Z-avarab@gmail.com>
64
-
65
-
66
-* bc/clarify-eol-attr (2022-01-12) 2 commits
67
- (merged to 'next' on 2022-02-04 at dc1db4bd21)
68
- + docs: correct documentation about eol attribute
69
- + t0027: add tests for eol without text in .gitattributes
70
-
71
- Doc and test update around the eol attribute.
72
- source: <20220111021507.531736-1-sandals@crustytoothpaste.net>
73
-
74
-
75
-* bc/csprng-mktemps (2022-01-17) 2 commits
76
- (merged to 'next' on 2022-02-04 at 2e32375c73)
77
- + wrapper: use a CSPRNG to generate random file names
78
- + wrapper: add a helper to generate numbers from a CSPRNG
79
-
80
- Pick a better random number generator and use it when we prepare
81
- temporary filenames.
82
- source: <20220117215617.843190-1-sandals@crustytoothpaste.net>
83
-
84
-
85
-* en/sparse-checkout-leakfix (2022-01-28) 1 commit
86
- (merged to 'next' on 2022-02-04 at 10ca176008)
87
- + sparse-checkout: fix a couple minor memory leaks
88
-
89
- Leakfix.
90
- source: <pull.1189.git.git.1643335098710.gitgitgadget@gmail.com>
53
+[New Topics]
54
55
+* ds/mailmap (2022-02-14) 1 commit
56
+ (merged to 'next' on 2022-02-14 at 1e50634951)
57
+ + mailmap: change primary address for Derrick Stolee
58
93
-* gh/doc-typos (2022-01-26) 2 commits
94
- (merged to 'next' on 2022-02-04 at b71e1bc746)
95
- + Documentation/config/pgp.txt: add missing apostrophe
96
- + Documentation/config/pgp.txt: replace stray <TAB> character with <SPC>
59
+ Update mailmap entries.
60
98
- Typofix.
99
- source: <20220126121426.53799-1-greg@hurrell.net>
61
+ Will merge to 'master'.
62
+ source: <pull.1142.git.1644857153590.gitgitgadget@gmail.com>
63
64
102
-* jc/doc-log-messages (2022-01-27) 3 commits
103
- (merged to 'next' on 2022-02-04 at cf136572ce)
104
- + SubmittingPatches: explain why we care about log messages
105
- + CodingGuidelines: hint why we value clearly written log messages
106
- + SubmittingPatches: write problem statement in the log in the present tense
65
+* bc/clarify-eol-attr (2022-02-14) 1 commit
66
+ (merged to 'next' on 2022-02-14 at 7e23e61f3f)
67
+ + doc: clarify interaction between 'eol' and text=auto
68
108
- Update the contributor-facing documents on proposed log messages.
109
- source: <20220126234205.2923388-1-gitster@pobox.com>
69
+ Documentation update
70
71
+ Will merge to 'master'.
72
+ source: <xmqqilth2u28.fsf@gitster.g>
73
112
-* rc/negotiate-only-typofix (2022-01-28) 1 commit
113
- (merged to 'next' on 2022-02-04 at 62b947ddbf)
114
- + fetch: fix negotiate-only error message
74
116
- Typofix.
117
- source: <20220128143602.31842-1-robert@coup.net.nz>
75
+* ab/date-mode-release (2022-02-14) 5 commits
76
+ - date API: add and use a date_mode_release()
77
+ - date API: add basic API docs
78
+ - date API: provide and use a DATE_MODE_INIT
79
+ - date API: create a date.h, split from cache.h
80
+ - cache.h: remove always unused show_date_human() declaration
81
82
+ Plug (some) memory leaks around parse_date_format().
83
+ source: <cover-v2-0.5-00000000000-20220204T235143Z-avarab@gmail.com>
84
120
-* rs/parse-options-lithelp-help (2022-01-20) 1 commit
121
- (merged to 'next' on 2022-02-04 at 74bc57e8fa)
122
- + parse-options: document bracketing of argh
85
+--------------------------------------------------
86
+[Stalled]
87
124
- Comment update.
125
- source: <c6ab4408-1091-4d14-849e-afe5f3053e8b@web.de>
88
+* je/http-better-error-output (2021-12-03) 1 commit
89
+ . http-backend: give a hint that web browser access is not supported
90
91
+ When the http-backend program, which is the server-side component
92
+ for the smart HTTP transport, sends a "404 Not found" error, we
93
+ deliberately did not say anything to the requesting client. We now
94
+ send a message back to the browser to tell the user that they do
95
+ not want to visit the URL via their browser, instead of a totally
96
+ blank page.
97
128
-* sy/diff-usage-typofix (2022-02-02) 1 commit
129
- (merged to 'next' on 2022-02-04 at 28a4186a44)
130
- + builtin/diff.c: fix "git-diff" usage string typo
98
+ Expecting a reroll.
99
+ Breaks its self tests.
100
+ cf. <7r23s082-o3q0-479o-srqn-r45q778s5nq7@vanv.qr>
101
+ source: <20211202102855.23907-1-jengelh@inai.de>
102
132
- Typofix.
133
- source: <20220202072844.35545-1-shaoxuan.yuan02@gmail.com>
103
104
+* cb/save-term-across-editor-invocation (2021-12-01) 3 commits
105
+ - fixup! editor: allow for saving/restoring terminal state
106
+ - editor: allow for saving/restoring terminal state
107
+ - terminal: teach save_term to fail when not foreground
108
136
-* tg/fetch-prune-exit-code-fix (2022-01-31) 1 commit
137
- (merged to 'next' on 2022-02-04 at 8af6ab286d)
138
- + fetch --prune: exit with error if pruning fails
109
+ Some editors are reported to leave the terminal in funny state
110
+ after they exit on Windows. Work it around by saving and restoring
111
+ the terminal state when needed.
112
140
- When "git fetch --prune" failed to prune the refs it wanted to
141
- prune, the command issued error messages but exited with exit
142
- status 0, which has been corrected.
143
- source: <20220131133047.1885074-1-t.gummerer@gmail.com>
113
+ Expecting a reroll.
114
+ cf. <CAPUEsphktbdxeV7hvF52Or3CVHS8oOk5-WV=xfEZa8kfCVVnVg@mail.gmail.com>
115
+ source: <20211202035446.1154-1-carenas@gmail.com>
116
117
--------------------------------------------------
146
-[New Topics]
118
+[Cooking]
119
120
* jc/glossary-worktree (2022-02-09) 1 commit
121
(merged to 'next' on 2022-02-10 at d05e2b6ea3)
@@ -167,22 +139,24 @@ Release tarballs are available at:
139
140
141
* hw/t1410-adjust-test-for-reftable (2022-02-09) 2 commits
170
- - t1410: mark bufsize boundary test as REFFILES
171
- - t1410: use test-tool ref-store to inspect reflogs
142
+ (merged to 'next' on 2022-02-14 at 6b96b4faa4)
143
+ + t1410: mark bufsize boundary test as REFFILES
144
+ + t1410: use test-tool ref-store to inspect reflogs
145
146
Fix tests that are unnecessarily specific to ref-files backend.
147
175
- Will merge to 'next'.
148
+ Will merge to 'master'.
149
source: <pull.1213.git.git.1644406180.gitgitgadget@gmail.com>
150
151
152
* ps/fetch-optim-with-commit-graph (2022-02-10) 2 commits
180
- - fetch: skip computing output width when not printing anything
181
- - fetch-pack: use commit-graph when computing cutoff
153
+ (merged to 'next' on 2022-02-14 at 2b331293fb)
154
+ + fetch: skip computing output width when not printing anything
155
+ + fetch-pack: use commit-graph when computing cutoff
156
157
A couple of optimization to "git fetch".
158
185
- Will merge to 'next'.
159
+ Will merge to 'master'.
160
source: <cover.1644495978.git.ps@pks.im>
161
162
@@ -197,11 +171,12 @@ Release tarballs are available at:
171
172
173
* sy/t0001-use-path-is-helper (2022-02-11) 1 commit
200
- - t0001: replace "test [-d|-f]" with test_path_is_* functions
174
+ (merged to 'next' on 2022-02-14 at 2f1bdb0803)
175
+ + t0001: replace "test [-d|-f]" with test_path_is_* functions
176
177
Test modernization.
178
204
- Will merge to 'next'.
179
+ Will merge to 'master'.
180
source: <20220121102109.433457-2-shaoxuan.yuan02@gmail.com>
181
182
@@ -226,15 +201,16 @@ Release tarballs are available at:
201
202
203
* ah/log-no-graph (2022-02-11) 2 commits
229
- - log: add a --no-graph option
230
- - log: fix memory leak if --graph is passed multiple times
204
+ (merged to 'next' on 2022-02-14 at 6c8fd1f37f)
205
+ + log: add a --no-graph option
206
+ + log: fix memory leak if --graph is passed multiple times
207
208
"git log --graph --graph" used to leak a graph structure, and there
209
was no way to countermand "--graph" that appear earlier on the
210
command line. A "--no-graph" option has been added and resource
235
- leakage lhas been plugged.
211
+ leakage has been plugged.
212
237
- Will merge to 'next'.
213
+ Will merge to 'master'.
214
source: <20220211163627.598166-2-alexhenrie24@gmail.com>
215
216
@@ -246,40 +222,6 @@ Release tarballs are available at:
222
Will merge to 'next'?
223
source: <20220211134655.1149320-1-cogoni.guillaume@gmail.com>
224
249
---------------------------------------------------
250
-[Stalled]
251
-
252
-* je/http-better-error-output (2021-12-03) 1 commit
253
- . http-backend: give a hint that web browser access is not supported
254
-
255
- When the http-backend program, which is the server-side component
256
- for the smart HTTP transport, sends a "404 Not found" error, we
257
- deliberately did not say anything to the requesting client. We now
258
- send a message back to the browser to tell the user that they do
259
- not want to visit the URL via their browser, instead of a totally
260
- blank page.
261
-
262
- Expecting a reroll.
263
- Breaks its self tests.
264
- cf. <7r23s082-o3q0-479o-srqn-r45q778s5nq7@vanv.qr>
265
- source: <20211202102855.23907-1-jengelh@inai.de>
266
-
267
-
268
-* cb/save-term-across-editor-invocation (2021-12-01) 3 commits
269
- - fixup! editor: allow for saving/restoring terminal state
270
- - editor: allow for saving/restoring terminal state
271
- - terminal: teach save_term to fail when not foreground
272
-
273
- Some editors are reported to leave the terminal in funny state
274
- after they exit on Windows. Work it around by saving and restoring
275
- the terminal state when needed.
276
-
277
- Expecting a reroll.
278
- cf. <CAPUEsphktbdxeV7hvF52Or3CVHS8oOk5-WV=xfEZa8kfCVVnVg@mail.gmail.com>
279
- source: <20211202035446.1154-1-carenas@gmail.com>
280
-
281
---------------------------------------------------
282
-[Cooking]
225
226
* ab/t0051-skip-on-non-windows (2022-02-04) 1 commit
227
(merged to 'next' on 2022-02-10 at 3e587df1d6)
@@ -361,15 +303,16 @@ Release tarballs are available at:
303
source: <abc67d757cb6b244cf54b7b030985180ce134724.1644434802.git.me@ttaylorr.com>
304
305
364
-* jc/cat-file-batch-commands (2022-02-11) 3 commits
306
+* jc/cat-file-batch-commands (2022-02-14) 4 commits
307
- cat-file: add --batch-command mode
308
+ - cat-file: add remove_timestamp helper
309
- cat-file: introduce batch_mode enum to replace print_contents
310
- cat-file: rename cmdmode to transform_mode
311
312
"git cat-file" learns "--batch-command" mode, which is a more
313
flexible interface than the existing "--batch" or "--batch-check"
314
modes, to allow different kinds of inquiries made.
372
- source: <pull.1212.v5.git.git.1644609683.gitgitgadget@gmail.com>
315
+ source: <pull.1212.v6.git.git.1644862988.gitgitgadget@gmail.com>
316
317
318
* ar/submodule-update (2022-02-10) 20 commits
@@ -591,7 +534,7 @@ Release tarballs are available at:
534
source: <cover-v2-0.2-00000000000-20220202T111228Z-avarab@gmail.com>
535
536
594
-* en/merge-tree (2022-02-02) 16 commits
537
+* en/merge-tree (2022-02-14) 13 commits
538
- git-merge-tree.txt: add a section on potentional usage mistakes
539
- merge-tree: add a --allow-unrelated-histories flag
540
- merge-tree: allow `ls-files -u` style info to be NUL terminated
@@ -599,10 +542,7 @@ Release tarballs are available at:
542
- merge-tree: provide a list of which files have conflicts
543
- merge-ort: provide a merge_get_conflicted_files() helper function
544
- merge-tree: support including merge messages in output
602
- - merge-ort: allow update messages to be written to different file stream
545
- merge-ort: split out a separate display_update_messages() function
604
- - diff: allow diff_warn_rename_limit to write somewhere besides stderr
605
- - Introduce a variant of the `warning()` function that takes a `FILE *`
546
- merge-tree: implement real merges
547
- merge-tree: add option parsing and initial shell for real merge function
548
- merge-tree: move logic for existing merge into new function
@@ -614,7 +554,7 @@ Release tarballs are available at:
554
tree that would be contained in the resulting merge commit, if the
555
histories leading to these two commits were to be merged, and is
556
added as a new mode of "git merge-tree" subcommand.
617
- source: <pull.1122.v3.git.1643787281.gitgitgadget@gmail.com>
557
+ source: <pull.1122.v4.git.1644698093.gitgitgadget@gmail.com>
558
559
560
* ll/doc-mktree-typofix (2022-02-02) 1 commit
@@ -836,11 +776,12 @@ Release tarballs are available at:
776
777
778
* bs/forbid-i18n-of-protocol-token-in-fetch-pack (2022-02-11) 1 commit
839
- - fetch-pack: parameterize message containing 'ready' keyword
779
+ (merged to 'next' on 2022-02-14 at 9abd0dce80)
780
+ + fetch-pack: parameterize message containing 'ready' keyword
781
782
L10n support for a few error messages.
783
843
- Will merge to 'next'.
784
+ Will merge to 'master'.
785
source: <20211222075805.19027-1-bagasdotme@gmail.com>
786
787