What's cooking (2024/04 #09)
Junio C Hamano committed
Apr 23, 2024 at 17:10 UTC
4210716096af6b518b13b85e97db636dee09eb2a
1 file changed
+220
-214
whats-cooking.txt
+220
-214
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Apr 2024, #08; Mon, 22)
3
-X-master-at: 00e10ef10e161a913893b8cb33aa080d4ca5baa6
4
-X-next-at: 0c9c63564e25443fb8d0688fe3c87722ba128238
2
+Subject: What's cooking in git.git (Apr 2024, #09; Tue, 23)
3
+X-master-at: bf995e7a4f94a9388aa8042dc9e338f3fcb75496
4
+X-next-at: d95f3e8691c1cba156beb6189d8229bc2ee0caab
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Apr 2024, #08; Mon, 22)
7
+What's cooking in git.git (Apr 2024, #09; Tue, 23)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -17,6 +17,8 @@ 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
+A release candidate Git 2.45-rc1 has been tagged.
21
+
22
Copies of the source code to Git live in many repositories, and the
23
following is a list of the ones I push into or their mirrors. Some
24
repositories have only a subset of branches.
@@ -46,108 +48,30 @@ Release tarballs are available at:
48
https://www.kernel.org/pub/software/scm/git/
49
50
--------------------------------------------------
49
-[New Topics]
50
-
51
-* aj/stash-staged-fix (2024-04-22) 1 commit
52
- - stash: fix "--staged" with binary files
53
-
54
- "git stash -S" did not handle binary files correctly, which has
55
- been corrected.
56
-
57
- Will merge to 'next'.
58
- source: <pull.1722.git.1713781694490.gitgitgadget@gmail.com>
59
-
60
-
61
-* rj/add-i-leak-fix (2024-04-22) 4 commits
62
- - add: plug a leak on interactive_add
63
- - add-patch: plug a leak handling the '/' command
64
- - add-interactive: plug a leak in get_untracked_files
65
- - apply: plug a leak in apply_data
66
-
67
- Leakfix.
68
-
69
- Will merge to 'next'.
70
- source: <69f86760-96ff-4c62-9649-4627652b7c19@gmail.com>
71
-
72
-
73
-* rj/add-p-typo-reaction (2024-04-21) 1 commit
74
- - add-patch: response to unknown command
75
-
76
- When the user responds to a prompt given by "git add -p" with an
77
- unsupported command, list of available commands were given, which
78
- was too much if the user knew what they wanted to type but merely
79
- made a typo. Now the user gets a much shorter error message.
80
-
81
- Will merge to 'next'.
82
- source: <b209a2b8-f98f-4f14-a687-9022d30968dd@gmail.com>
83
-
84
-
85
-* rs/vsnprintf-failure-is-not-a-bug (2024-04-21) 1 commit
86
- - don't report vsnprintf(3) error as bug
87
-
88
- Demote a BUG() to an die() when the failure from vsnprintf() may
89
- not be due to a programmer error.
90
-
91
- Will merge to 'next'.
92
- source: <ea752a2b-9b74-4a59-a037-4782abf7161e@web.de>
93
-
94
---------------------------------------------------
95
-[Cooking]
96
-
97
-* ds/format-patch-rfc-and-k (2024-04-19) 1 commit
98
- - format-patch: ensure that --rfc and -k are mutually exclusive
99
-
100
- The "-k" and "--rfc" options of "format-patch" will now error out
101
- when used together, as one tells us not to add anything to the
102
- title of the commit, and the other one tells us to add "RFC" in
103
- addition to "PATCH".
104
-
105
- Will merge to 'next'.
106
- source: <71d195c248879e7c46fac0e84c6b0a8aa90bd2c2.1713488563.git.dsimic@manjaro.org>
107
-
108
-
109
-* jc/format-patch-rfc-more (2024-04-22) 2 commits
110
- - format-patch: "--rfc=-(WIP)" appends to produce [PATCH (WIP)]
111
- - format-patch: allow --rfc to optionally take a value, like --rfc=WIP
112
-
113
- The "--rfc" option of "git format-patch" learned to take an
114
- optional string value to be used in place of "RFC" to tweak the
115
- "[PATCH]" on the subject header.
116
-
117
- Will merge to 'next'?
118
- source: <20240421185915.1031590-1-gitster@pobox.com>
119
-
120
-
121
-* ps/the-index-is-no-more (2024-04-18) 6 commits
122
- - repository: drop `initialize_the_repository()`
123
- - repository: drop `the_index` variable
124
- - builtin/clone: stop using `the_index`
125
- - repository: initialize index in `repo_init()`
126
- - builtin: stop using `the_index`
127
- - t/helper: stop using `the_index`
128
-
129
- The singleton index_state instance "the_index" has been eliminated
130
- by always instantiating "the_repository" and replacing references
131
- to "the_index" with references to its .index member.
51
+[Graduated to 'master']
52
133
- Comments?
134
- source: <cover.1713442061.git.ps@pks.im>
53
+* dd/t9604-use-posix-timezones (2024-04-10) 1 commit
54
+ (merged to 'next' on 2024-04-16 at 46ab81737f)
55
+ + t9604: Fix test for musl libc and new Debian
56
57
+ The cvsimport tests required that the platform understands
58
+ traditional timezone notations like CST6CDT, which has been
59
+ updated to work on those systems as long as they understand
60
+ POSIX notation with explicit tz transition dates.
61
+ source: <20240410032812.30476-1-congdanhqx@gmail.com>
62
137
-* pw/rebase-m-signoff-fix (2024-04-18) 6 commits
138
- - rebase -m: fix --signoff with conflicts
139
- - sequencer: store commit message in private context
140
- - sequencer: move current fixups to private context
141
- - sequencer: start removing private fields from public API
142
- - sequencer: always free "struct replay_opts"
143
- - Merge branch 'pw/t3428-cleanup' into pw/rebase-m-signoff-fix
63
145
- "git rebase --signoff" used to forget that it needs to add a
146
- sign-off to the resulting commit when told to continue after a
147
- conflict stops its operation.
64
+* la/format-trailer-info (2024-03-15) 5 commits
65
+ (merged to 'next' on 2024-04-16 at dca4784407)
66
+ + trailer: finish formatting unification
67
+ + trailer: begin formatting unification
68
+ + format_trailer_info(): append newline for non-trailer lines
69
+ + format_trailer_info(): drop redundant unfold_value()
70
+ + format_trailer_info(): use trailer_item objects
71
+ (this branch is used by la/hide-trailer-info.)
72
149
- Will merge to 'next'.
150
- source: <cover.1713445918.git.phillip.wood@dunelm.org.uk>
73
+ The code to format trailers have been cleaned up.
74
+ source: <pull.1694.git.1710485706.gitgitgadget@gmail.com>
75
76
77
* mr/rerere-crash-fix (2024-04-16) 1 commit
@@ -157,8 +81,6 @@ Release tarballs are available at:
81
When .git/rr-cache/ rerere database gets corrupted or rerere is fed to
82
work on a file with conflicted hunks resolved incompletely, the rerere
83
machinery got confused and segfaulted, which has been corrected.
160
-
161
- Will merge to 'master'.
84
source: <20240416105320.1113401-1-marcel@roethke.info>
85
86
@@ -170,8 +92,6 @@ Release tarballs are available at:
92
culprit, we used to show it in a format that does not honor common
93
UI tweaks, like log.date and log.decorate. The code has been
94
taught to use "git show" to follow more customizations.
173
-
174
- Will merge to 'master'.
95
source: <965ae345-fd58-c46c-5a7a-de181e901f21@softwolves.pp.se>
96
97
@@ -182,11 +102,38 @@ Release tarballs are available at:
102
GIt 2.44 introduced a regression that makes the updated code to
103
barf in repositories with multi-pack index written by older
104
versions of Git, which has been corrected.
185
-
186
- Will merge to 'master'.
105
source: <a8251f8278ba9a3b41a8e299cb4918a62df6d1c7.1713163238.git.ps@pks.im>
106
107
108
+* ps/reftable-block-iteration-optim (2024-04-15) 10 commits
109
+ (merged to 'next' on 2024-04-15 at 3a2353c7f2)
110
+ + reftable/block: avoid copying block iterators on seek
111
+ + reftable/block: reuse `zstream` state on inflation
112
+ + reftable/block: open-code call to `uncompress2()`
113
+ + reftable/block: reuse uncompressed blocks
114
+ + reftable/reader: iterate to next block in place
115
+ + reftable/block: move ownership of block reader into `struct table_iter`
116
+ + reftable/block: introduce `block_reader_release()`
117
+ + reftable/block: better grouping of functions
118
+ + reftable/block: merge `block_iter_seek()` and `block_reader_seek()`
119
+ + reftable/block: rename `block_reader_start()`
120
+
121
+ The code to iterate over reftable blocks has seen some optimization
122
+ to reduce memory allocation and deallocation.
123
+ source: <cover.1712578376.git.ps@pks.im>
124
+
125
+
126
+* ps/run-auto-maintenance-in-receive-pack (2024-04-17) 2 commits
127
+ (merged to 'next' on 2024-04-22 at cacdcac452)
128
+ + builtin/receive-pack: convert to use git-maintenance(1)
129
+ + run-command: introduce function to prepare auto-maintenance process
130
+
131
+ The "receive-pack" program (which responds to "git push") was not
132
+ converted to run "git maintenance --auto" when other codepaths that
133
+ used to run "git gc --auto" were updated, which has been corrected.
134
+ source: <cover.1713334241.git.ps@pks.im>
135
+
136
+
137
* rj/launch-editor-error-message (2024-04-15) 1 commit
138
(merged to 'next' on 2024-04-16 at 3d0dd46fc2)
139
+ launch_editor: waiting message on error
@@ -195,18 +142,23 @@ Release tarballs are available at:
142
line after launching an editor, and then append another error
143
message on the same line if the editor errors out. It now clears
144
the "waiting for..." line before giving the error message.
198
-
199
- Will merge to 'master'.
145
source: <e208da74-8f16-44ae-912e-ae968da82057@gmail.com>
146
147
148
+* rs/apply-reject-long-name (2024-04-16) 1 commit
149
+ (merged to 'next' on 2024-04-17 at 701ccded8b)
150
+ + apply: avoid using fixed-size buffer in write_out_one_reject()
151
+
152
+ The filename used for rejected hunks "git apply --reject" creates
153
+ was limited to PATH_MAX, which has been lifted.
154
+ source: <a93cd243-cb17-4ad5-8d23-30768dc5213b@web.de>
155
+
156
+
157
* rs/imap-send-simplify-cmd-issuing-codepath (2024-04-15) 1 commit
158
(merged to 'next' on 2024-04-17 at 0255e49f8b)
159
+ imap-send: increase command size limit
160
161
Code simplification.
208
-
209
- Will merge to 'master'.
162
source: <7026075c-db4e-4d43-bbd1-d2edb52da9b7@web.de>
163
164
@@ -215,30 +167,173 @@ Release tarballs are available at:
167
+ git-compat-util: fix NO_OPENSSL on current macOS
168
169
Build fix.
218
-
219
- Will merge to 'master'.
170
source: <3188f4e2-9744-40b1-8f05-0896b8679d25@web.de>
171
172
173
+* ta/fast-import-parse-path-fix (2024-04-15) 8 commits
174
+ (merged to 'next' on 2024-04-15 at 00cc71a679)
175
+ + fast-import: make comments more precise
176
+ + fast-import: forbid escaped NUL in paths
177
+ + fast-import: document C-style escapes for paths
178
+ + fast-import: improve documentation for path quoting
179
+ + fast-import: remove dead strbuf
180
+ + fast-import: allow unquoted empty path for root
181
+ + fast-import: directly use strbufs for paths
182
+ + fast-import: tighten path unquoting
183
+
184
+ The way "git fast-import" handles paths described in its input has
185
+ been tightened up and more clearly documented.
186
+ source: <cover.1713056559.git.thalia@archibald.dev>
187
+
188
+
189
+* xx/rfc2822-date-format-in-doc (2024-04-12) 1 commit
190
+ (merged to 'next' on 2024-04-17 at f2186bd6e8)
191
+ + Documentation: fix typos describing date format
192
+
193
+ Docfix.
194
+ source: <pull.1716.git.1712911876943.gitgitgadget@gmail.com>
195
+
196
+
197
* yb/replay-doc-linkfix (2024-04-15) 1 commit
198
(merged to 'next' on 2024-04-15 at e8cf9cd9a8)
199
+ Documentation: fix linkgit reference
200
201
Docfix.
202
+ source: <pull.1706.git.git.1713132482976.gitgitgadget@gmail.com>
203
+
204
+--------------------------------------------------
205
+[New Topics]
206
+
207
+* ps/undecided-is-not-necessarily-sha1 (2024-04-23) 12 commits
208
+ - repository: stop setting SHA1 as the default object hash
209
+ - builtin/shortlog: don't set up revisions without repo
210
+ - builtin/diff: explicitly set hash algo when there is no repo
211
+ - builtin/bundle: abort "verify" early when there is no repository
212
+ - builtin/blame: don't access potentially unitialized `the_hash_algo`
213
+ - builtin/rev-parse: allow shortening to more than 40 hex characters
214
+ - remote-curl: fix parsing of detached SHA256 heads
215
+ - attr: fix BUG() when parsing attrs outside of repo
216
+ - attr: don't recompute default attribute source
217
+ - parse-options-cb: only abbreviate hashes when hash algo is known
218
+ - path: move `validate_headref()` to its only user
219
+ - path: harden validation of HEAD with non-standard hashes
220
+
221
+ Before discovering the repository details, We used to assume SHA-1
222
+ as the "default" hash function, which has been corrected. Hopefully
223
+ this will smoke out codepaths that rely on such an unwarranted
224
+ assumptions.
225
+
226
+ Will merge to 'next'?
227
+ source: <cover.1713848619.git.ps@pks.im>
228
+
229
+--------------------------------------------------
230
+[Cooking]
231
+
232
+* aj/stash-staged-fix (2024-04-22) 1 commit
233
+ (merged to 'next' on 2024-04-23 at d49e9dade0)
234
+ + stash: fix "--staged" with binary files
235
+
236
+ "git stash -S" did not handle binary files correctly, which has
237
+ been corrected.
238
+
239
+ Will cook in 'next'.
240
+ source: <pull.1722.git.1713781694490.gitgitgadget@gmail.com>
241
+
242
+
243
+* rj/add-i-leak-fix (2024-04-22) 4 commits
244
+ (merged to 'next' on 2024-04-23 at b10e350a54)
245
+ + add: plug a leak on interactive_add
246
+ + add-patch: plug a leak handling the '/' command
247
+ + add-interactive: plug a leak in get_untracked_files
248
+ + apply: plug a leak in apply_data
249
+
250
+ Leakfix.
251
252
Will merge to 'master'.
230
- source: <pull.1706.git.git.1713132482976.gitgitgadget@gmail.com>
253
+ source: <69f86760-96ff-4c62-9649-4627652b7c19@gmail.com>
254
255
233
-* rs/apply-reject-long-name (2024-04-16) 1 commit
234
- (merged to 'next' on 2024-04-17 at 701ccded8b)
235
- + apply: avoid using fixed-size buffer in write_out_one_reject()
256
+* rj/add-p-typo-reaction (2024-04-21) 1 commit
257
+ (merged to 'next' on 2024-04-23 at 8ac0509b47)
258
+ + add-patch: response to unknown command
259
+
260
+ When the user responds to a prompt given by "git add -p" with an
261
+ unsupported command, list of available commands were given, which
262
+ was too much if the user knew what they wanted to type but merely
263
+ made a typo. Now the user gets a much shorter error message.
264
+
265
+ Will cook in 'next'.
266
+ source: <b209a2b8-f98f-4f14-a687-9022d30968dd@gmail.com>
267
237
- The filename used for rejected hunks "git apply --reject" creates
238
- was limited to PATH_MAX, which has been lifted.
268
+
269
+* rs/vsnprintf-failure-is-not-a-bug (2024-04-21) 1 commit
270
+ (merged to 'next' on 2024-04-23 at bf66ab6ea7)
271
+ + don't report vsnprintf(3) error as bug
272
+
273
+ Demote a BUG() to an die() when the failure from vsnprintf() may
274
+ not be due to a programmer error.
275
276
Will merge to 'master'.
241
- source: <a93cd243-cb17-4ad5-8d23-30768dc5213b@web.de>
277
+ source: <ea752a2b-9b74-4a59-a037-4782abf7161e@web.de>
278
+
279
+
280
+* ds/format-patch-rfc-and-k (2024-04-19) 1 commit
281
+ (merged to 'next' on 2024-04-23 at b3b0c5507a)
282
+ + format-patch: ensure that --rfc and -k are mutually exclusive
283
+
284
+ The "-k" and "--rfc" options of "format-patch" will now error out
285
+ when used together, as one tells us not to add anything to the
286
+ title of the commit, and the other one tells us to add "RFC" in
287
+ addition to "PATCH".
288
+
289
+ Will cook in 'next'.
290
+ source: <71d195c248879e7c46fac0e84c6b0a8aa90bd2c2.1713488563.git.dsimic@manjaro.org>
291
+
292
+
293
+* jc/format-patch-rfc-more (2024-04-23) 2 commits
294
+ (merged to 'next' on 2024-04-23 at 9f51487974)
295
+ + format-patch: "--rfc=-(WIP)" appends to produce [PATCH (WIP)]
296
+ + format-patch: allow --rfc to optionally take a value, like --rfc=WIP
297
+
298
+ The "--rfc" option of "git format-patch" learned to take an
299
+ optional string value to be used in place of "RFC" to tweak the
300
+ "[PATCH]" on the subject header.
301
+
302
+ Will cook in 'next'.
303
+ source: <20240423175234.170434-1-gitster@pobox.com>
304
+
305
+
306
+* ps/the-index-is-no-more (2024-04-18) 6 commits
307
+ - repository: drop `initialize_the_repository()`
308
+ - repository: drop `the_index` variable
309
+ - builtin/clone: stop using `the_index`
310
+ - repository: initialize index in `repo_init()`
311
+ - builtin: stop using `the_index`
312
+ - t/helper: stop using `the_index`
313
+
314
+ The singleton index_state instance "the_index" has been eliminated
315
+ by always instantiating "the_repository" and replacing references
316
+ to "the_index" with references to its .index member.
317
+
318
+ Comments?
319
+ source: <cover.1713442061.git.ps@pks.im>
320
+
321
+
322
+* pw/rebase-m-signoff-fix (2024-04-18) 6 commits
323
+ (merged to 'next' on 2024-04-23 at 66374c00e2)
324
+ + rebase -m: fix --signoff with conflicts
325
+ + sequencer: store commit message in private context
326
+ + sequencer: move current fixups to private context
327
+ + sequencer: start removing private fields from public API
328
+ + sequencer: always free "struct replay_opts"
329
+ + Merge branch 'pw/t3428-cleanup' into pw/rebase-m-signoff-fix
330
+
331
+ "git rebase --signoff" used to forget that it needs to add a
332
+ sign-off to the resulting commit when told to continue after a
333
+ conflict stops its operation.
334
+
335
+ Will cook in 'next'.
336
+ source: <cover.1713445918.git.phillip.wood@dunelm.org.uk>
337
338
339
* js/for-each-repo-keep-going (2024-04-18) 2 commits
@@ -255,43 +350,18 @@ Release tarballs are available at:
350
source: <pull.1719.v2.git.1713444783.gitgitgadget@gmail.com>
351
352
258
-* ps/run-auto-maintenance-in-receive-pack (2024-04-17) 2 commits
259
- (merged to 'next' on 2024-04-22 at cacdcac452)
260
- + builtin/receive-pack: convert to use git-maintenance(1)
261
- + run-command: introduce function to prepare auto-maintenance process
262
-
263
- The "receive-pack" program (which responds to "git push") was not
264
- converted to run "git maintenance --auto" when other codepaths that
265
- used to run "git gc --auto" were updated, which has been corrected.
266
-
267
- Will merge to 'master'.
268
- source: <cover.1713334241.git.ps@pks.im>
269
-
270
-
353
* xx/disable-replace-when-building-midx (2024-04-17) 1 commit
272
- - midx: disable replace objects
354
+ (merged to 'next' on 2024-04-23 at 6c8f41740e)
355
+ + midx: disable replace objects
356
357
The procedure to build multi-pack-index got confused by the
358
replace-refs mechanism, which has been corrected by disabling the
359
latter.
360
278
- Will merge to 'next'.
361
+ Will cook in 'next'.
362
source: <pull.1711.v2.git.1712554017808.gitgitgadget@gmail.com>
363
364
282
-* dd/t9604-use-posix-timezones (2024-04-10) 1 commit
283
- (merged to 'next' on 2024-04-16 at 46ab81737f)
284
- + t9604: Fix test for musl libc and new Debian
285
-
286
- The cvsimport tests required that the platform understands
287
- traditional timezone notations like CST6CDT, which has been
288
- updated to work on those systems as long as they understand
289
- POSIX notation with explicit tz transition dates.
290
-
291
- Will merge to 'master'.
292
- source: <20240410032812.30476-1-congdanhqx@gmail.com>
293
-
294
-
365
* kn/update-ref-symrefs (2024-04-12) 8 commits
366
- SQUASH???
367
- refs: support symrefs in 'reference-transaction' hook
@@ -305,34 +375,6 @@ Release tarballs are available at:
375
source: <20240412095908.1134387-1-knayak@gitlab.com>
376
377
308
-* ta/fast-import-parse-path-fix (2024-04-15) 8 commits
309
- (merged to 'next' on 2024-04-15 at 00cc71a679)
310
- + fast-import: make comments more precise
311
- + fast-import: forbid escaped NUL in paths
312
- + fast-import: document C-style escapes for paths
313
- + fast-import: improve documentation for path quoting
314
- + fast-import: remove dead strbuf
315
- + fast-import: allow unquoted empty path for root
316
- + fast-import: directly use strbufs for paths
317
- + fast-import: tighten path unquoting
318
-
319
- The way "git fast-import" handles paths described in its input has
320
- been tightened up and more clearly documented.
321
-
322
- Will merge to 'master'.
323
- source: <cover.1713056559.git.thalia@archibald.dev>
324
-
325
-
326
-* xx/rfc2822-date-format-in-doc (2024-04-12) 1 commit
327
- (merged to 'next' on 2024-04-17 at f2186bd6e8)
328
- + Documentation: fix typos describing date format
329
-
330
- Docfix.
331
-
332
- Will merge to 'master'.
333
- source: <pull.1716.git.1712911876943.gitgitgadget@gmail.com>
334
-
335
-
378
* la/doc-use-of-contacts-when-contributing (2024-04-18) 8 commits
379
- SubmittingPatches: demonstrate using git-contacts with git-send-email
380
- SubmittingPatches: add heading for format-patch and send-email
@@ -347,7 +389,7 @@ Release tarballs are available at:
389
ask review for their patches, a bit more in our developer
390
documentation.
391
350
- Will merge to 'next'?
392
+ Will merge to 'next'.
393
source: <pull.1704.v6.git.1713477125.gitgitgadget@gmail.com>
394
395
@@ -426,26 +468,6 @@ Release tarballs are available at:
468
source: <20240328101356.300374-1-e@80x24.org>
469
470
429
-* ps/reftable-block-iteration-optim (2024-04-15) 10 commits
430
- (merged to 'next' on 2024-04-15 at 3a2353c7f2)
431
- + reftable/block: avoid copying block iterators on seek
432
- + reftable/block: reuse `zstream` state on inflation
433
- + reftable/block: open-code call to `uncompress2()`
434
- + reftable/block: reuse uncompressed blocks
435
- + reftable/reader: iterate to next block in place
436
- + reftable/block: move ownership of block reader into `struct table_iter`
437
- + reftable/block: introduce `block_reader_release()`
438
- + reftable/block: better grouping of functions
439
- + reftable/block: merge `block_iter_seek()` and `block_reader_seek()`
440
- + reftable/block: rename `block_reader_start()`
441
-
442
- The code to iterate over reftable blocks has seen some optimization
443
- to reduce memory allocation and deallocation.
444
-
445
- Will merge to 'master'.
446
- source: <cover.1712578376.git.ps@pks.im>
447
-
448
-
471
* bc/credential-scheme-enhancement (2024-04-16) 16 commits
472
- credential: add method for querying capabilities
473
- credential-cache: implement authtype capability
@@ -516,11 +538,10 @@ Release tarballs are available at:
538
- trailer: add unit tests for trailer iterator
539
- Makefile: sort UNIT_TEST_PROGRAMS
540
- Merge branch 'la/format-trailer-info' into la/hide-trailer-info
519
- (this branch uses la/format-trailer-info.)
541
542
The trailer API has been reshuffled a bit.
543
523
- Needs review.
544
+ Will merge to 'next'.
545
source: <pull.1696.v2.git.1713504153.gitgitgadget@gmail.com>
546
547
@@ -534,21 +555,6 @@ Release tarballs are available at:
555
source: <97bdaf075bf5a68554cca1731eca78aff2662907.1710444774.git.dsimic@manjaro.org>
556
557
537
-* la/format-trailer-info (2024-03-15) 5 commits
538
- (merged to 'next' on 2024-04-16 at dca4784407)
539
- + trailer: finish formatting unification
540
- + trailer: begin formatting unification
541
- + format_trailer_info(): append newline for non-trailer lines
542
- + format_trailer_info(): drop redundant unfold_value()
543
- + format_trailer_info(): use trailer_item objects
544
- (this branch is used by la/hide-trailer-info.)
545
-
546
- The code to format trailers have been cleaned up.
547
-
548
- Will merge to 'master'.
549
- source: <pull.1694.git.1710485706.gitgitgadget@gmail.com>
550
-
551
-
558
* ie/config-includeif-hostname (2024-03-19) 2 commits
559
- config: learn the "hostname:" includeIf condition
560
- t: add a test helper for getting hostname