What's cooking (2023/04 #08)
Junio C Hamano committed
Apr 27, 2023 at 16:34 UTC
3c458ad37697396dc3cc35bb194da2ac49cb9fc7
1 file changed
+181
-273
whats-cooking.txt
+181
-273
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Apr 2023, #07; Tue, 25)
3
-X-master-at: 2807bd2c10606e590886543afe4e4f208dddd489
4
-X-next-at: 96c395b00cfdcc2a001874b3e5d6fadf5fd01d38
2
+Subject: What's cooking in git.git (Apr 2023, #08; Thu, 27)
3
+X-master-at: f85cd430b12b0d3e4f1a30ef3239a1b73d5f6331
4
+X-next-at: f1e218fcd8619b15a0125c091d4134e60ed764f1
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Apr 2023, #07; Tue, 25)
7
+What's cooking in git.git (Apr 2023, #08; Thu, 27)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -50,215 +50,92 @@ Release tarballs are available at:
50
--------------------------------------------------
51
[Graduated to 'master']
52
53
-* ah/format-patch-thread-doc (2023-04-03) 1 commit
54
- (merged to 'next' on 2023-04-14 at acf141a832)
55
- + format-patch: correct documentation of --thread without an argument
56
-
57
- Doc update.
58
- source: <20230403040724.642513-1-alexhenrie24@gmail.com>
59
-
60
-
61
-* en/header-split-cache-h (2023-04-18) 25 commits
62
- (merged to 'next' on 2023-04-18 at 55b4d95cac)
63
- + protocol.h: move definition of DEFAULT_GIT_PORT from cache.h
64
- (merged to 'next' on 2023-04-13 at b9afefff0b)
65
- + mailmap, quote: move declarations of global vars to correct unit
66
- + treewide: reduce includes of cache.h in other headers
67
- + treewide: remove double forward declaration of read_in_full
68
- + cache.h: remove unnecessary includes
69
- + treewide: remove cache.h inclusion due to pager.h changes
70
- + pager.h: move declarations for pager.c functions from cache.h
71
- + treewide: remove cache.h inclusion due to editor.h changes
72
- + editor: move editor-related functions and declarations into common file
73
- + treewide: remove cache.h inclusion due to object.h changes
74
- + object.h: move some inline functions and defines from cache.h
75
- + treewide: remove cache.h inclusion due to object-file.h changes
76
- + object-file.h: move declarations for object-file.c functions from cache.h
77
- + treewide: remove cache.h inclusion due to git-zlib changes
78
- + git-zlib: move declarations for git-zlib functions from cache.h
79
- + treewide: remove cache.h inclusion due to object-name.h changes
80
- + object-name.h: move declarations for object-name.c functions from cache.h
81
- + treewide: remove unnecessary cache.h inclusion
82
- + treewide: be explicit about dependence on mem-pool.h
83
- + treewide: be explicit about dependence on oid-array.h
84
- + treewide: be explicit about dependence on pack-revindex.h
85
- + treewide: be explicit about dependence on convert.h
86
- + treewide: be explicit about dependence on advice.h
87
- + treewide: be explicit about dependence on trace.h & trace2.h
88
- + Merge branch 'ab/remove-implicit-use-of-the-repository' into en/header-split-cache-h
89
- (this branch is used by en/header-split-cache-h-part-2.)
90
-
91
- Header clean-up.
92
- source: <pull.1509.v3.git.1681182060.gitgitgadget@gmail.com>
93
-
94
-
95
-* fc/doc-stop-using-manversion (2023-04-10) 1 commit
96
- (merged to 'next' on 2023-04-14 at 0800fe5ab4)
97
- + doc: simplify man version
98
- (this branch is used by fc/doc-use-datestamp-in-commit.)
99
-
100
- Doc build simplification.
101
- source: <20230408001829.11031-1-felipe.contreras@gmail.com>
102
-
103
-
104
-* jk/protocol-cap-parse-fix (2023-04-14) 7 commits
105
- (merged to 'next' on 2023-04-17 at fd9bf05656)
106
- + v0 protocol: use size_t for capability length/offset
107
- + t5512: test "ls-remote --heads --symref" filtering with v0 and v2
108
- + t5512: allow any protocol version for filtered symref test
109
- + t5512: add v2 support for "ls-remote --symref" test
110
- + v0 protocol: fix sha1/sha256 confusion for capabilities^{}
111
- + t5512: stop referring to "v1" protocol
112
- + v0 protocol: fix infinite loop when parsing multi-valued capabilities
113
-
114
- The code to parse capability list for v0 on-wire protocol fell into
115
- an infinite loop when a capability appears multiple times, which
116
- has been corrected.
117
- source: <20230414212404.GA639653@coredump.intra.peff.net>
118
-
119
-
120
-* ow/ref-filter-omit-empty (2023-04-13) 1 commit
121
- (merged to 'next' on 2023-04-14 at 2798986c60)
122
- + branch, for-each-ref, tag: add option to omit empty lines
123
-
124
- "git branch --format=..." and "git format-patch --format=..."
125
- learns "--omit-empty" to hide refs that whose formatting result
126
- becomes an empty string from the output.
127
- source: <20230407175316.6404-1-oystwa@gmail.com>
128
-
129
-
130
-* ps/fix-geom-repack-with-alternates (2023-04-14) 10 commits
131
- (merged to 'next' on 2023-04-18 at de56e80363)
132
- + repack: disable writing bitmaps when doing a local repack
133
- + repack: honor `-l` when calculating pack geometry
134
- + t/helper: allow chmtime to print verbosely without modifying mtime
135
- + pack-objects: extend test coverage of `--stdin-packs` with alternates
136
- + pack-objects: fix error when same packfile is included and excluded
137
- + pack-objects: fix error when packing same pack twice
138
- + pack-objects: split out `--stdin-packs` tests into separate file
139
- + repack: fix generating multi-pack-index with only non-local packs
140
- + repack: fix trying to use preferred pack in alternates
141
- + midx: fix segfault with no packs and invalid preferred pack
142
-
143
- Geometric repacking ("git repack --geometric=<n>") in a repository
144
- that borrows from an alternate object database had various corner
145
- case bugs, which have been corrected.
146
- source: <cover.1681452028.git.ps@pks.im>
147
-
148
-
149
-* rj/send-email-validate-hook-count-messages (2023-04-14) 1 commit
150
- (merged to 'next' on 2023-04-18 at 0c3db0bd3b)
151
- + send-email: export patch counters in validate environment
152
-
153
- The sendemail-validate validate hook learned to pass the total
154
- number of input files and where in the sequence each invocation is
155
- via environment variables.
156
- source: <20230414155249.667180-1-robin@jarry.cc>
157
-
158
-
159
-* rn/sparse-describe (2023-04-03) 1 commit
160
- (merged to 'next' on 2023-04-14 at 9699cfad2c)
161
- + describe: enable sparse index for describe
162
-
163
- "git describe --dirty" learns to work better with sparse-index.
164
- source: <20230403164749.246001-1-nanth.raghul@gmail.com>
165
-
166
-
167
-* rs/archive-from-subdirectory-fixes (2023-03-24) 1 commit
168
- (merged to 'next' on 2023-04-14 at 950f9ed807)
169
- + archive: improve support for running in subdirectory
170
-
171
- "git archive" run from a subdirectory mishandled attributes and
172
- paths outside the current directory.
173
- source: <7c33b01b-7b2a-25fa-9a66-1e65cd12bc84@web.de>
174
-
175
---------------------------------------------------
176
-[New Topics]
177
-
178
-* ek/completion-use-read-r-to-read-literally (2023-04-20) 1 commit
179
- (merged to 'next' on 2023-04-24 at 25bf3b808b)
180
- + completion: suppress unwanted unescaping of `read`
53
+* ds/fsck-pack-revindex (2023-04-17) 5 commits
54
+ (merged to 'next' on 2023-04-19 at 6fb9527bf5)
55
+ + fsck: validate .rev file header
56
+ + fsck: check rev-index position values
57
+ + fsck: check rev-index checksums
58
+ + fsck: create scaffolding for rev-index checks
59
+ + Merge branch 'tb/pack-revindex-on-disk' into ds/fsck-pack-revindex
60
+ (this branch uses tb/pack-revindex-on-disk.)
61
182
- The completion script used to use bare "read" without the "-r"
183
- option to read the contents of various state files, which risked
184
- getting confused with backslashes in them. This has been
185
- corrected.
62
+ "git fsck" learned to validate the on-disk pack reverse index files.
63
+ source: <pull.1512.git.1681748502.gitgitgadget@gmail.com>
64
187
- Will merge to 'master'.
188
- source: <20230420223800.1698197-1-myoga.murase@gmail.com>
65
66
+* fc/doc-checkout-markup-updates (2023-04-18) 2 commits
67
+ (merged to 'next' on 2023-04-20 at 62782d75c4)
68
+ + doc: git-checkout: reorganize examples
69
+ + doc: git-checkout: trivial callout cleanup
70
191
-* pw/rebase-i-after-failure (2023-04-21) 6 commits
192
- - rebase -i: fix adding failed command to the todo list
193
- - rebase: fix rewritten list for failed pick
194
- - rebase --continue: refuse to commit after failed command
195
- - sequencer: factor out part of pick_commits()
196
- - rebase -i: remove patch file after conflict resolution
197
- - rebase -i: move unlink() calls
71
+ Doc mark-up update.
72
+ source: <20230418070048.2209469-1-felipe.contreras@gmail.com>
73
199
- Various fixes to the behaviour of "rebase -i" when the command got
200
- interrupted by conflicting changes.
74
202
- Needs review.
203
- source: <pull.1492.v2.git.1682089074.gitgitgadget@gmail.com>
75
+* fc/doc-use-datestamp-in-commit (2023-04-14) 3 commits
76
+ (merged to 'next' on 2023-04-20 at 3b6ccb62ec)
77
+ + doc: set actual revdate for manpages
78
+ + Merge branch 'fc/doc-stop-using-manversion' into fc/doc-use-datestamp-in-commit
79
+ + Merge branch 'fc/remove-header-workarounds-for-asciidoc' into fc/doc-use-datestamp-in-commit
80
81
+ Instead of the time the formatter was run, show the timestamp
82
+ recorded in the commit in the documentation.
83
+ source: <20230413074722.71260-1-felipe.contreras@gmail.com>
84
206
-* jk/blame-fake-commit-label (2023-04-24) 1 commit
207
- - blame: use different author name for fake commit generated by --contents
85
209
- The output given by "git blame" that attributes a line to contents
210
- taken from the file specified by the "--contents" option shows it
211
- differently from a line attributed to the working tree file.
86
+* tb/pack-revindex-on-disk (2023-04-13) 7 commits
87
+ (merged to 'next' on 2023-04-19 at d6b90b44cf)
88
+ + t: invert `GIT_TEST_WRITE_REV_INDEX`
89
+ + config: enable `pack.writeReverseIndex` by default
90
+ + pack-revindex: introduce `pack.readReverseIndex`
91
+ + pack-revindex: introduce GIT_TEST_REV_INDEX_DIE_ON_DISK
92
+ + pack-revindex: make `load_pack_revindex` take a repository
93
+ + t5325: mark as leak-free
94
+ + pack-write.c: plug a leak in stage_tmp_packfiles()
95
+ (this branch is used by ds/fsck-pack-revindex.)
96
213
- Will merge to 'next'.
214
- source: <20230424193508.2245566-1-jacob.e.keller@intel.com>
97
+ The on-disk reverse index that allows mapping from the pack offset
98
+ to the object name for the object stored at the offset has been
99
+ enabled by default.
100
+ source: <cover.1681338013.git.me@ttaylorr.com>
101
102
+--------------------------------------------------
103
+[New Topics]
104
217
-* jk/misc-null-check-fixes (2023-04-24) 2 commits
218
- - fetch_bundle_uri(): drop pointless NULL check
219
- - notes: clean up confusing NULL checks in init_notes()
105
+* hx/negotiator-non-recursive (2023-04-26) 2 commits
106
+ - negotiator/skipping: fix some problems in mark_common()
107
+ - negotiator/default: avoid stack overflow
108
221
- Code clean-up.
109
+ The implementation of the default "negotiator", used to find common
110
+ ancestor over the network for object tranfer, used to be recursive;
111
+ it was updated to be iterative to conserve stackspace usage.
112
223
- Will merge to 'next'.
224
- source: <20230422135455.GA3942740@coredump.intra.peff.net>
113
+ Comments?
114
+ source: <cover.1682513384.git.hanxin.hx@bytedance.com>
115
116
227
-* jk/parse-commit-with-malformed-ident (2023-04-25) 4 commits
228
- - parse_commit(): describe more date-parsing failure modes
229
- - parse_commit(): handle broken whitespace-only timestamp
230
- - parse_commit(): parse timestamp from end of line
231
- - t4212: avoid putting git on left-hand side of pipe
117
+* jc/doc-clarify-git-default-hash-variable (2023-04-26) 1 commit
118
+ - doc: GIT_DEFAULT_HASH is and will be ignored during "clone"
119
233
- The commit object parser has been taught to be a bit more lenient
234
- to parse timestamps on the author/committer line with a malformed
235
- author/committer ident.
120
+ The documentation was misleading about the interaction between
121
+ GIT_DEFAULT_HASH and "git clone", which has been clarified to
122
+ stress that the variable is to be ignored by the command.
123
124
Will merge to 'next'?
238
- Protecting against mischieves using \f and \v may be worth doing.
239
- source: <20230425055244.GA4014505@coredump.intra.peff.net>
240
-
241
-
242
-* sl/sparse-write-tree-part-2 (2023-04-24) 1 commit
243
- - write-tree: optimize sparse integration
125
+ source: <xmqqzg6uvfpo.fsf_-_@gitster.g>
126
245
- Fix-up to a topic already graduated to 'master'.
127
247
- Iffy.
248
- source: <20230423071243.1863977-1-cheskaqiqi@gmail.com>
128
+* mh/fix-detect-compilers-with-nondigit-versions (2023-04-26) 1 commit
129
+ - Handle some compiler versions containing a dash
130
131
+ The detect-compilers script to help auto-tweaking the build system
132
+ had trouble working with compilers whose version number has extra
133
+ suffixes. The script has been taught that certain suffixes (like
134
+ "-win32" in "gcc 10-win32") can be safely stripped as they share
135
+ the same features and bugs with the version without the suffix.
136
251
-* tb/pack-bitmap-traversal-with-boundary (2023-04-25) 3 commits
252
- - pack-bitmap.c: use commit boundary during bitmap traversal
253
- - pack-bitmap.c: extract `fill_in_bitmap()`
254
- - revision: support tracking uninteresting commits
255
-
256
- The object traversal using reachability bitmap done by
257
- "pack-object" has been tweaked to take advantage of the fact that
258
- using "boundary" commits as representative of all the uninteresting
259
- ones can save quite a lot of object enumeration.
260
-
261
- source: <cover.1682380788.git.me@ttaylorr.com>
137
+ Will merge to 'next'.
138
+ source: <20230426004843.3391826-1-mh@glandium.org>
139
140
--------------------------------------------------
141
[Stalled]
@@ -326,20 +203,6 @@ Release tarballs are available at:
203
source: <pull.1474.git.1675614276549.gitgitgadget@gmail.com>
204
205
329
-* tl/notes-separator (2023-04-25) 6 commits
330
- - notes.c: introduce "--[no-]stripspace" option
331
- - notes.c: append separator instead of insert by pos
332
- - notes.c: introduce '--separator=<paragraph-break>' option
333
- - t3321: add test cases about the notes stripspace behavior
334
- - notes.c: use designated initializers for clarity
335
- - notes.c: cleanup 'strbuf_grow' call in 'append_edit'
336
-
337
- 'git notes append' was taught '--separator' to specify string to insert
338
- between paragraphs.
339
-
340
- source: <cover.1682429602.git.dyroneteng@gmail.com>
341
-
342
-
206
* ab/tag-object-type-errors (2022-11-22) 5 commits
207
- tag: don't emit potentially incorrect "object is a X, not a Y"
208
- tag: don't misreport type of tagged objects in errors
@@ -430,6 +293,108 @@ Release tarballs are available at:
293
--------------------------------------------------
294
[Cooking]
295
296
+* tl/notes-separator (2023-04-25) 6 commits
297
+ - notes.c: introduce "--[no-]stripspace" option
298
+ - notes.c: append separator instead of insert by pos
299
+ - notes.c: introduce '--separator=<paragraph-break>' option
300
+ - t3321: add test cases about the notes stripspace behavior
301
+ - notes.c: use designated initializers for clarity
302
+ - notes.c: cleanup 'strbuf_grow' call in 'append_edit'
303
+
304
+ 'git notes append' was taught '--separator' to specify string to insert
305
+ between paragraphs.
306
+
307
+ Will merge to 'next'?
308
+ Looking good.
309
+ source: <cover.1682429602.git.dyroneteng@gmail.com>
310
+
311
+
312
+* ek/completion-use-read-r-to-read-literally (2023-04-20) 1 commit
313
+ (merged to 'next' on 2023-04-24 at 25bf3b808b)
314
+ + completion: suppress unwanted unescaping of `read`
315
+
316
+ The completion script used to use bare "read" without the "-r"
317
+ option to read the contents of various state files, which risked
318
+ getting confused with backslashes in them. This has been
319
+ corrected.
320
+
321
+ Will merge to 'master'.
322
+ source: <20230420223800.1698197-1-myoga.murase@gmail.com>
323
+
324
+
325
+* pw/rebase-i-after-failure (2023-04-21) 6 commits
326
+ - rebase -i: fix adding failed command to the todo list
327
+ - rebase: fix rewritten list for failed pick
328
+ - rebase --continue: refuse to commit after failed command
329
+ - sequencer: factor out part of pick_commits()
330
+ - rebase -i: remove patch file after conflict resolution
331
+ - rebase -i: move unlink() calls
332
+
333
+ Various fixes to the behaviour of "rebase -i" when the command got
334
+ interrupted by conflicting changes.
335
+
336
+ Needs review.
337
+ source: <pull.1492.v2.git.1682089074.gitgitgadget@gmail.com>
338
+
339
+
340
+* jk/blame-fake-commit-label (2023-04-24) 1 commit
341
+ (merged to 'next' on 2023-04-26 at 85226d9501)
342
+ + blame: use different author name for fake commit generated by --contents
343
+
344
+ The output given by "git blame" that attributes a line to contents
345
+ taken from the file specified by the "--contents" option shows it
346
+ differently from a line attributed to the working tree file.
347
+
348
+ Will merge to 'master'.
349
+ source: <20230424193508.2245566-1-jacob.e.keller@intel.com>
350
+
351
+
352
+* jk/misc-null-check-fixes (2023-04-24) 2 commits
353
+ (merged to 'next' on 2023-04-26 at 9500384e9d)
354
+ + fetch_bundle_uri(): drop pointless NULL check
355
+ + notes: clean up confusing NULL checks in init_notes()
356
+
357
+ Code clean-up.
358
+
359
+ Will merge to 'master'.
360
+ source: <20230422135455.GA3942740@coredump.intra.peff.net>
361
+
362
+
363
+* jk/parse-commit-with-malformed-ident (2023-04-27) 4 commits
364
+ - parse_commit(): describe more date-parsing failure modes
365
+ - parse_commit(): handle broken whitespace-only timestamp
366
+ - parse_commit(): parse timestamp from end of line
367
+ - t4212: avoid putting git on left-hand side of pipe
368
+
369
+ The commit object parser has been taught to be a bit more lenient
370
+ to parse timestamps on the author/committer line with a malformed
371
+ author/committer ident.
372
+
373
+ Will merge to 'next'.
374
+ source: <20230427081330.GA1461786@coredump.intra.peff.net>
375
+
376
+
377
+* sl/sparse-write-tree-part-2 (2023-04-24) 1 commit
378
+ - write-tree: optimize sparse integration
379
+
380
+ Fix-up to a topic already graduated to 'master'.
381
+
382
+ Iffy.
383
+ source: <20230423071243.1863977-1-cheskaqiqi@gmail.com>
384
+
385
+
386
+* tb/pack-bitmap-traversal-with-boundary (2023-04-25) 3 commits
387
+ - pack-bitmap.c: use commit boundary during bitmap traversal
388
+ - pack-bitmap.c: extract `fill_in_bitmap()`
389
+ - revision: support tracking uninteresting commits
390
+
391
+ The object traversal using reachability bitmap done by
392
+ "pack-object" has been tweaked to take advantage of the fact that
393
+ using "boundary" commits as representative of all the uninteresting
394
+ ones can save quite a lot of object enumeration.
395
+ source: <cover.1682380788.git.me@ttaylorr.com>
396
+
397
+
398
* ar/config-count-tests-updates (2023-04-24) 3 commits
399
- t1300: add tests for missing keys
400
- t1300: check stderr for "ignores pairs" tests
@@ -467,17 +432,6 @@ Release tarballs are available at:
432
source: <pull.1517.v2.git.1682194649.gitgitgadget@gmail.com>
433
434
470
-* fc/doc-checkout-markup-updates (2023-04-18) 2 commits
471
- (merged to 'next' on 2023-04-20 at 62782d75c4)
472
- + doc: git-checkout: reorganize examples
473
- + doc: git-checkout: trivial callout cleanup
474
-
475
- Doc mark-up update.
476
-
477
- Will merge to 'master'.
478
- source: <20230418070048.2209469-1-felipe.contreras@gmail.com>
479
-
480
-
435
* jk/gpg-trust-level-fix (2023-04-19) 1 commit
436
(merged to 'next' on 2023-04-21 at eb8413dc9d)
437
+ gpg-interface: set trust level of missing key to "undefined"
@@ -490,7 +444,7 @@ Release tarballs are available at:
444
source: <20230419012957.GA503941@coredump.intra.peff.net>
445
446
493
-* ps/fetch-output-format (2023-04-19) 8 commits
447
+* ps/fetch-output-format (2023-04-27) 8 commits
448
- fetch: introduce machine-parseable "porcelain" output format
449
- fetch: introduce new `--output-format` option
450
- fetch: move option related variables into main function
@@ -502,9 +456,7 @@ Release tarballs are available at:
456
457
"git fetch" learned the "--output-format" option that emits what it
458
did in a machine-parseable format.
505
-
506
- Needs review.
507
- source: <cover.1681906948.git.ps@pks.im>
459
+ source: <cover.1682593865.git.ps@pks.im>
460
461
462
* en/ort-finalize-after-0-merges-fix (2023-04-24) 1 commit
@@ -530,21 +482,6 @@ Release tarballs are available at:
482
source: <20230420205350.600760-1-szeder.dev@gmail.com>
483
484
533
-* ds/fsck-pack-revindex (2023-04-17) 5 commits
534
- (merged to 'next' on 2023-04-19 at 6fb9527bf5)
535
- + fsck: validate .rev file header
536
- + fsck: check rev-index position values
537
- + fsck: check rev-index checksums
538
- + fsck: create scaffolding for rev-index checks
539
- + Merge branch 'tb/pack-revindex-on-disk' into ds/fsck-pack-revindex
540
- (this branch uses tb/pack-revindex-on-disk.)
541
-
542
- "git fsck" learned to validate the on-disk pack reverse index files.
543
-
544
- Will merge to 'master'.
545
- source: <pull.1512.git.1681748502.gitgitgadget@gmail.com>
546
-
547
-
485
* tb/enable-cruft-packs-by-default (2023-04-18) 10 commits
486
(merged to 'next' on 2023-04-21 at 068bf86fc3)
487
+ repository.h: drop unused `gc_cruft_packs`
@@ -618,38 +555,6 @@ Release tarballs are available at:
555
source: <cover.1681326818.git.code@khaugsbakk.name>
556
557
621
-* tb/pack-revindex-on-disk (2023-04-13) 7 commits
622
- (merged to 'next' on 2023-04-19 at d6b90b44cf)
623
- + t: invert `GIT_TEST_WRITE_REV_INDEX`
624
- + config: enable `pack.writeReverseIndex` by default
625
- + pack-revindex: introduce `pack.readReverseIndex`
626
- + pack-revindex: introduce GIT_TEST_REV_INDEX_DIE_ON_DISK
627
- + pack-revindex: make `load_pack_revindex` take a repository
628
- + t5325: mark as leak-free
629
- + pack-write.c: plug a leak in stage_tmp_packfiles()
630
- (this branch is used by ds/fsck-pack-revindex.)
631
-
632
- The on-disk reverse index that allows mapping from the pack offset
633
- to the object name for the object stored at the offset has been
634
- enabled by default.
635
-
636
- Will merge to 'master'.
637
- source: <cover.1681338013.git.me@ttaylorr.com>
638
-
639
-
640
-* fc/doc-use-datestamp-in-commit (2023-04-14) 3 commits
641
- (merged to 'next' on 2023-04-20 at 3b6ccb62ec)
642
- + doc: set actual revdate for manpages
643
- + Merge branch 'fc/doc-stop-using-manversion' into fc/doc-use-datestamp-in-commit
644
- + Merge branch 'fc/remove-header-workarounds-for-asciidoc' into fc/doc-use-datestamp-in-commit
645
-
646
- Instead of the time the formatter was run, show the timestamp
647
- recorded in the commit in the documentation.
648
-
649
- Will merge to 'master'.
650
- source: <20230413074722.71260-1-felipe.contreras@gmail.com>
651
-
652
-
558
* pb/complete-and-document-auto-merge-and-friends (2023-04-14) 5 commits
559
(merged to 'next' on 2023-04-20 at 2728a01622)
560
+ completion: complete AUTO_MERGE
@@ -666,15 +571,18 @@ Release tarballs are available at:
571
source: <pull.1515.git.1681495119.gitgitgadget@gmail.com>
572
573
669
-* tb/ban-strtok (2023-04-24) 6 commits
670
- - banned.h: mark `strtok()` and `strtok_r()` as banned
671
- - t/helper/test-json-writer.c: avoid using `strtok()`
672
- - t/helper/test-oidmap.c: avoid using `strtok()`
673
- - t/helper/test-hashmap.c: avoid using `strtok()`
674
- - string-list: introduce `string_list_setlen()`
675
- - string-list: multi-delimiter `string_list_split_in_place()`
574
+* tb/ban-strtok (2023-04-27) 6 commits
575
+ (merged to 'next' on 2023-04-27 at cbbfa4a609)
576
+ + banned.h: mark `strtok()` and `strtok_r()` as banned
577
+ + t/helper/test-json-writer.c: avoid using `strtok()`
578
+ + t/helper/test-oidmap.c: avoid using `strtok()`
579
+ + t/helper/test-hashmap.c: avoid using `strtok()`
580
+ + string-list: introduce `string_list_setlen()`
581
+ + string-list: multi-delimiter `string_list_split_in_place()`
582
583
Mark strtok() and strtok_r() to be banned.
584
+
585
+ Will merge to 'master'.
586
source: <cover.1682374789.git.me@ttaylorr.com>
587
588