What's cooking (2022/04 #06)
Junio C Hamano committed
Apr 25, 2022 at 16:26 UTC
fc403878a9fad6613031c3df306b8856a59d11b9
1 file changed
+300
-92
whats-cooking.txt
+300
-92
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
Bcc: lwn@lwn.net
3
-Subject: What's cooking in git.git (Apr 2022, #05; Mon, 18)
3
+Subject: What's cooking in git.git (Apr 2022, #06; Mon, 25)
4
X-master-at: 6cd33dceed60949e2dbc32e3f0f5e67c4c882e1e
5
X-next-at: b9c8b46e9451eb1f82393119d53aa151b6f7ff83
6
7
-What's cooking in git.git (Apr 2022, #05; Mon, 18)
7
+What's cooking in git.git (Apr 2022, #06; Mon, 25)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -13,14 +13,34 @@ 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
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.
16
+There are a handful of regressions we managed to sneak into the 2.36
17
+release that we need to fix before we can move forward. For some
18
+reason, the release turned out to be unusually bad in the recent
19
+history X-<.
20
23
-cCopies of the source code to Git live in many repositories, and the
21
+Here are what I know about, with or without fixes that have been
22
+reviewed satisfactorily:
23
+
24
+ - "diff-tree --stdin <pathspec>" loses <pathspec> after showing one
25
+ comparison.
26
+ cf. <xmqqbkwpvyyc.fsf@gitster.g>
27
+
28
+ - "submodule update" without <pathspec> makes unnecessary noise
29
+ when skipping uninitialized submodules.
30
+ cf. <pull.1258.v2.git.git.1650890741430.gitgitgadget@gmail.com>
31
+
32
+ - hooks no longer is connected directly to the standard output.
33
+ cf. <CA+dzEBn108QoMA28f0nC8K21XT+Afua0V2Qv8XkR8rAeqUCCZw@mail.gmail.com>
34
+
35
+ - "sudo make install" does not work out-of-the-box.
36
+ cf. <4ef9287b-6260-9538-7c89-cffb611520ee@maurel.de>
37
+
38
+And there are some that are not recent regressions:
39
+
40
+ - "name-rev" frees some strings it still uses prematurely.
41
+ cf. <Ylw+M5wwUYKcLM+M@voi.aagh.net>
42
+
43
+Copies of the source code to Git live in many repositories, and the
44
following is a list of the ones I push into or their mirrors. Some
45
repositories have only a subset of branches.
46
@@ -49,27 +69,210 @@ Release tarballs are available at:
69
https://www.kernel.org/pub/software/scm/git/
70
71
--------------------------------------------------
52
-[Graduated to 'master']
72
+[New Topics]
73
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
74
+* ah/rebase-keep-base-fix (2022-04-21) 1 commit
75
+ - rebase: use correct base for --keep-base when a branch is given
76
59
- A couple of work around for CI breaking warnings from gcc 12.
60
- source: <20220415231342.35980-1-carenas@gmail.com>
77
+ "git rebase --keep-base <upstream> <branch-to-rebase>" computed the
78
+ commit to rebase onto incorrectly, which has been corrected.
79
62
---------------------------------------------------
63
-[New Topics]
80
+ Will merge to 'next'.
81
+ source: <20220421044233.894255-1-alexhenrie24@gmail.com>
82
+
83
+
84
+* cg/tools-for-git-doc (2022-04-21) 1 commit
85
+ - Documentation/ToolsForGit.txt: Tools for developing Git
86
+
87
+ A new doc that lists tips for tools to work with Git's codebase.
88
+
89
+ Thoughts?
90
+ source: <20220421084515.21236-2-cogoni.guillaume@gmail.com>
91
65
-* cm/reftable-0-length-memset (2022-04-15) 1 commit
66
- - reftable: avoid undefined behaviour breaking t0032
92
+
93
+* ea/rebase-code-simplify (2022-04-20) 1 commit
94
+ - rebase: simplify an assignment of options.type in cmd_rebase
95
96
Code clean-up.
97
70
- Will merge to 'next'?
71
- source: <20220415083058.29495-1-carenas@gmail.com>
98
+ Will merge to 'next'.
99
+ source: <20220418172721.215898-1-eantoranz@gmail.com>
100
+
101
+
102
+* kt/commit-graph-plug-fp-leak-on-error (2022-04-20) 1 commit
103
+ - commit-graph: close file before returning NULL
104
+
105
+ Fix a leak of FILE * in an error codepath.
106
+
107
+ Will merge to 'next'.
108
+ source: <pull.1213.git.1650302007395.gitgitgadget@gmail.com>
109
+
110
+
111
+* ab/valgrind-fixes (2022-04-21) 4 commits
112
+ - object-file: fix a unpack_loose_header() regression in 3b6a8db3b03
113
+ - commit-graph.c: don't assume that stat() succeeds
114
+ - log test: skip a failing mkstemp() test under valgrind
115
+ - tests: make RUNTIME_PREFIX compatible with --valgrind
116
+
117
+ A bit of test framework fixes with a few fixes to issues found by
118
+ valgrind.
119
+
120
+ Expecting a reroll.
121
+ source: <cover-0.4-00000000000-20220421T200733Z-avarab@gmail.com>
122
+
123
+
124
+* cb/ci-make-p4-optional (2022-04-23) 5 commits
125
+ - fixup! CI: use https, not http to download binaries from perforce.com
126
+ - CI: use https, not http to download binaries from perforce.com
127
+ - ci: reintroduce prevention from perforce being quarantined in macOS
128
+ - ci: avoid brew for installing perforce
129
+ - ci: make failure to find perforce more user friendly
130
+
131
+ macOS CI jobs have been occasionally flaky due to tentative version
132
+ skew between perforce and the homebrew packager. Instead of
133
+ failing the whole CI job, just let it skip the p4 tests when this
134
+ happens.
135
+
136
+ Expecting a reroll.
137
+ source: <20220423142559.32507-1-carenas@gmail.com>
138
+ source: <0220423142559.32507-5-carenas@gmail.com>
139
+
140
+
141
+* ds/midx-normalize-pathname-before-comparison (2022-04-25) 3 commits
142
+ - cache: use const char * for get_object_directory()
143
+ - multi-pack-index: use --object-dir real path
144
+ - midx: use real paths in lookup_multi_pack_index()
145
+
146
+ The path taken by "git multi-pack-index" command from the end user
147
+ was compared with path internally prepared by the tool withut first
148
+ normalizing, which lead to duplicated paths not being noticed,
149
+ which has been corrected.
150
+
151
+ Will merge to 'next'.
152
+ source: <pull.1221.v2.git.1650911234.gitgitgadget@gmail.com>
153
+
154
+
155
+* jc/show-branch-g-current (2022-04-21) 1 commit
156
+ - show-branch: -g and --current are incompatible
157
+
158
+ The "--current" option of "git show-branch" should have been made
159
+ incompatible with the "--reflog" mode, but this was not enforced,
160
+ which has been corrected.
161
+ source: <xmqqh76mf7s4.fsf_-_@gitster.g>
162
+
163
+
164
+* rs/external-diff-tempfile (2022-04-20) 2 commits
165
+ - diff: use mks_tempfile_dt()
166
+ - tempfile: add mks_tempfile_dt()
167
+
168
+ The temporary files fed to external diff command are now generated
169
+ inside a new temporary directory under the same basename.
170
+
171
+ Will merge to 'next'.
172
+ source: <2ad1dd80-e79f-7304-219c-db24bb269c4d@web.de>
173
+
174
+
175
+* ab/cc-package-fixes (2022-04-22) 1 commit
176
+ - CI: select CC based on CC_PACKAGE (again)
177
+
178
+ Correct choices of C compilers used in various CI jobs.
179
+
180
+ Will merge to 'next'.
181
+ source: <patch-v3-1.1-8b3444ecc87-20220422T092015Z-avarab@gmail.com>
182
+
183
+
184
+* ab/hooks-regression-fix (2022-04-21) 6 commits
185
+ - hook API: fix v2.36.0 regression: hooks should be connected to a TTY
186
+ - hook API: don't redundantly re-set "no_stdin" and "stdout_to_stderr"
187
+ - hook tests: fix redirection logic error in 96e7225b310
188
+ - run-command: add an "ungroup" option to run_process_parallel()
189
+ - run-command tests: test stdout of run_command_parallel()
190
+ - run-command API: replace run_processes_parallel_tr2() with opts struct
191
+
192
+ In Git 2.36 we revamped the way how hooks are invoked. One change
193
+ that is end-user visible is that the output of a hook is no longer
194
+ directly connected to the standard output of "git" that spawns the
195
+ hook, which was noticed post release. This is getting corrected.
196
+
197
+ Expecting a reroll.
198
+ source: <cover-0.6-00000000000-20220421T122108Z-avarab@gmail.com>
199
+
200
+
201
+* ar/send-email-confirm-by-default (2022-04-22) 1 commit
202
+ - send-email: always confirm by default
203
+
204
+ "git send-email" is changed so that by default it asks for
205
+ confirmation before sending each message out.
206
+
207
+ Thoughts?
208
+ source: <20220422083629.1404989-1-hi@alyssa.is>
209
+
210
+
211
+* mv/log-since-as-filter (2022-04-23) 1 commit
212
+ - log: "--since-as-filter" option is a non-terminating "--since" variant
213
214
+ "git log --since=X" will stop traversal upon seeing a commit that
215
+ is older than X, but there may be commits behind it that is younger
216
+ than X when the commit was created with a faulty clock. A new
217
+ option is added to keep digging without stopping, and instead
218
+ filter out commits with timestamp older than X.
219
+
220
+ Will merge to 'next'.
221
+ source: <YmP4TaYmSEi6GeB4@vmiklos.hu>
222
+
223
+
224
+* rs/name-rev-fix-free-after-use (2022-04-23) 1 commit
225
+ - Revert "name-rev: release unused name strings"
226
+
227
+ Regression fix for 2.36 where "git name-rev" started to sometimes
228
+ reference strings after they are freed.
229
+
230
+ Will merge to 'next' and then to 'master'.
231
+ source: <340c8810-d912-7b18-d46e-a9d43f20216a@web.de>
232
+
233
+
234
+* ds/do-not-call-bug-on-bad-refs (2022-04-25) 1 commit
235
+ - clone: die() instead of BUG() on bad refs
236
+
237
+ Code clean-up.
238
+
239
+ Will merge to 'next'.
240
+ source: <pull.1214.v2.git.1650894450441.gitgitgadget@gmail.com>
241
+
242
+
243
+* gc/submodule-update-part2 (2022-04-25) 2 commits
244
+ - SQUASH??? tests to protect the fix
245
+ - submodule--helper: fix initialization of warn_if_uninitialized
246
+
247
+ "git submodule update" without pathspec should silently skip an
248
+ uninitialized submodule, but it started to become noisy by mistake.
249
+
250
+ Will merge to 'next' and then to 'master'.
251
+ source: <pull.1258.v2.git.git.1650890741430.gitgitgadget@gmail.com>
252
+
253
+
254
+* jc/diff-free-must-free-only-per-iteration-resources (2022-04-25) 2 commits
255
+ - t4013: diff-tree --stdin with pathspec
256
+ - 2.36 gitk/diff-tree --stdin regression fix
257
+
258
+ "diff-tree --stdin <pathspec>" lost the pathspec for second and
259
+ later commits, which broke "gitk".
260
+
261
+ Will merge to 'next' and then to 'master'.
262
+ source: <xmqqbkwpvyyc.fsf@gitster.g>
263
+
264
+
265
+* vd/sparse-stash (2022-04-25) 7 commits
266
+ - unpack-trees: preserve index sparsity
267
+ - stash: merge applied stash with merge-ort
268
+ - merge-recursive: add merge function arg to 'merge_recursive_generic'
269
+ - read-cache: set sparsity when index is new
270
+ - sparse-index: expose 'is_sparse_index_allowed()'
271
+ - stash: integrate with sparse index
272
+ - stash: expand sparse-checkout compatibility testing
273
+
274
+ Teach "git stash" to work better with sparse index entries.
275
+ source: <pull.1171.git.1650908957.gitgitgadget@gmail.com>
276
277
--------------------------------------------------
278
[Stalled]
@@ -126,6 +329,15 @@ Release tarballs are available at:
329
--------------------------------------------------
330
[Cooking]
331
332
+* cm/reftable-0-length-memset (2022-04-15) 1 commit
333
+ - reftable: avoid undefined behaviour breaking t0032
334
+
335
+ Code clean-up.
336
+
337
+ Will merge to 'next'.
338
+ source: <20220415083058.29495-1-carenas@gmail.com>
339
+
340
+
341
* sa/t1011-use-helpers (2022-04-12) 1 commit
342
- t1011: replace test -f with test_path_is_file
343
@@ -314,64 +526,64 @@ Release tarballs are available at:
526
Plug the memory leaks from the trickiest API of all, the revision
527
walker.
528
317
- Will merge to 'next'.
529
+ On hold.
530
source: <cover-v6-00.27-00000000000-20220413T195935Z-avarab@gmail.com>
531
532
321
-* ab/ci-github-workflow-markup (2022-04-14) 7 commits
322
- - ci: call `finalize_test_case_output` a little later
323
- - ci: use `--github-workflow-markup` in the GitHub workflow
324
- - ci: optionally mark up output in the GitHub workflow
325
- - test(junit): avoid line feeds in XML attributes
326
- - tests: refactor --write-junit-xml code
327
- - ci: make it easier to find failed tests' logs in the GitHub workflow
328
- - Merge branch 'ab/ci-setup-simplify' into ab/ci-github-workflow-markup
533
+* ab/ci-github-workflow-markup (2022-04-21) 11 commits
534
+ . ci: call `finalize_test_case_output` a little later
535
+ . ci: use `--github-workflow-markup` in the GitHub workflow
536
+ . ci: optionally mark up output in the GitHub workflow
537
+ . test(junit): avoid line feeds in XML attributes
538
+ . tests: refactor --write-junit-xml code
539
+ . ci: make it easier to find failed tests' logs in the GitHub workflow
540
+ . CI: stop setting FAILED_TEST_ARTIFACTS N times
541
+ . CI: don't include "test-results/" in ci/print-test-failures.sh output
542
+ . CI: add --exit-code to ci/print-test-failures.sh
543
+ . CI: don't "cd" in ci/print-test-failures.sh
544
+ . Merge branch 'ab/ci-setup-simplify' into ab/ci-github-workflow-markup
545
(this branch uses ab/ci-setup-simplify.)
546
547
Build a moral equivalent of js/ci-github-workflow-markup on top of
548
ab/ci-setup-simplify.
333
-
334
- How well does this compare feature-wise with js/ci-github-workflow-markup?
335
- source: <RFC-cover-v4-0.6-00000000000-20220413T195514Z-avarab@gmail.com>
336
-
337
-
338
-* ab/ci-setup-simplify (2022-04-14) 29 commits
339
- - CI: make it easy to use ci/*.sh outside of CI
340
- - CI: don't use "set -x" in "ci/lib.sh" output
341
- - CI: set PYTHON_PATH setting for osx-{clang,gcc} into "$jobname" case
342
- - CI: set SANITIZE=leak in MAKEFLAGS directly
343
- - CI: set CC in MAKEFLAGS directly, don't add it to the environment
344
- - CI: add more variables to MAKEFLAGS, except under vs-build
345
- - CI: narrow down variable definitions in --build and --test
346
- - CI: only invoke ci/lib.sh as "steps" in main.yml
347
- - CI: pre-select test slice in Windows & VS tests
348
- - ci/run-test-slice.sh: replace shelling out with "echo"
349
- - CI: move "env" definitions into ci/lib.sh
350
- - CI: combine ci/install{,-docker}-dependencies.sh
351
- - CI: split up and reduce "ci/test-documentation.sh"
352
- - CI: invoke "make artifacts-tar" directly in windows-build
353
- - CI: check ignored unignored build artifacts in "win[+VS] build" too
354
- - ci/lib.sh: use "test" instead of "["
355
- - CI: remove "run-build-and-tests.sh", run "make [test]" directly
356
- - CI: export variables via a wrapper
357
- - CI: consistently use "export" in ci/lib.sh
358
- - CI: move p4 and git-lfs variables to ci/install-dependencies.sh
359
- - CI: have "static-analysis" run "check-builtins", not "documentation"
360
- - CI: have "static-analysis" run a "make ci-static-analysis" target
361
- - CI: don't have "git grep" invoke a pager in tree content check
362
- - CI/lib.sh: stop adding leading whitespace to $MAKEFLAGS
363
- - CI: remove unused Azure ci/* code
364
- - CI: remove dead "tree skipping" code
365
- - CI: remove more dead Travis CI support
366
- - CI: make "$jobname" explicit, remove fallback
367
- - CI: run "set -ex" early in ci/lib.sh
549
+ source: <RFC-cover-v5-00.10-00000000000-20220421T183001Z-avarab@gmail.com>
550
+
551
+
552
+* ab/ci-setup-simplify (2022-04-21) 29 commits
553
+ . CI: make it easy to use ci/*.sh outside of CI
554
+ . CI: don't use "set -x" in "ci/lib.sh" output
555
+ . CI: set PYTHON_PATH setting for osx-{clang,gcc} into "$jobname" case
556
+ . CI: set SANITIZE=leak in MAKEFLAGS directly
557
+ . CI: set CC in MAKEFLAGS directly, don't add it to the environment
558
+ . CI: add more variables to MAKEFLAGS, except under vs-build
559
+ . CI: narrow down variable definitions in --build and --test
560
+ . CI: only invoke ci/lib.sh as "steps" in main.yml
561
+ . CI: pre-select test slice in Windows & VS tests
562
+ . ci/run-test-slice.sh: replace shelling out with "echo"
563
+ . CI: move "env" definitions into ci/lib.sh
564
+ . CI: combine ci/install{,-docker}-dependencies.sh
565
+ . CI: split up and reduce "ci/test-documentation.sh"
566
+ . CI: invoke "make artifacts-tar" directly in windows-build
567
+ . CI: check ignored unignored build artifacts in "win[+VS] build" too
568
+ . CI: make ci/{lib,install-dependencies}.sh POSIX-compatible
569
+ . CI: remove "run-build-and-tests.sh", run "make [test]" directly
570
+ . CI: export variables via a wrapper
571
+ . CI: consistently use "export" in ci/lib.sh
572
+ . CI: move p4 and git-lfs variables to ci/install-dependencies.sh
573
+ . CI: have "static-analysis" run "check-builtins", not "documentation"
574
+ . CI: have "static-analysis" run a "make ci-static-analysis" target
575
+ . CI: don't have "git grep" invoke a pager in tree content check
576
+ . CI/lib.sh: stop adding leading whitespace to $MAKEFLAGS
577
+ . CI: remove unused Azure ci/* code
578
+ . CI: remove dead "tree skipping" code
579
+ . CI: remove more dead Travis CI support
580
+ . CI: make "$jobname" explicit, remove fallback
581
+ . CI: run "set -ex" early in ci/lib.sh
582
(this branch is used by ab/ci-github-workflow-markup.)
583
584
Drive more actions done in CI via the Makefile instead of shell
585
commands sprinkled in .github/workflows/main.yml
372
-
373
- Will merge to 'next'?
374
- source: <cover-v3-00.29-00000000000-20220413T194847Z-avarab@gmail.com>
586
+ source: <cover-v5-00.29-00000000000-20220421T181526Z-avarab@gmail.com>
587
588
589
* kf/p4-multiple-remotes (2022-03-21) 1 commit
@@ -433,10 +645,10 @@ Release tarballs are available at:
645
source: <pull.1134.v5.git.1648616734.gitgitgadget@gmail.com>
646
647
436
-* en/sparse-cone-becomes-default (2022-03-13) 9 commits
648
+* en/sparse-cone-becomes-default (2022-04-21) 9 commits
649
- Documentation: some sparsity wording clarifications
650
- git-sparse-checkout.txt: mark non-cone mode as deprecated
439
- - git-sparse-checkout.txt: flesh out non-cone mode pattern discussion a bit
651
+ - git-sparse-checkout.txt: flesh out pattern set sections a bit
652
- git-sparse-checkout.txt: add a new EXAMPLES section
653
- git-sparse-checkout.txt: shuffle some sections and mark as internal
654
- git-sparse-checkout.txt: update docs for deprecation of 'init'
@@ -447,7 +659,7 @@ Release tarballs are available at:
659
Deprecate non-cone mode of the sparse-checkout feature.
660
661
Will merge to 'next'?
450
- source: <pull.1148.v2.git.1647054681.gitgitgadget@gmail.com>
662
+ source: <pull.1148.v3.git.1650594746.gitgitgadget@gmail.com>
663
664
665
* tb/cruft-packs (2022-03-02) 17 commits
@@ -479,23 +691,21 @@ Release tarballs are available at:
691
692
693
* js/ci-github-workflow-markup (2022-03-01) 9 commits
482
- . ci: call `finalize_test_case_output` a little later
483
- . ci: use `--github-workflow-markup` in the GitHub workflow
484
- . ci: optionally mark up output in the GitHub workflow
485
- . test(junit): avoid line feeds in XML attributes
486
- . tests: refactor --write-junit-xml code
487
- . ci/run-build-and-tests: add some structure to the GitHub workflow output
488
- . ci: make it easier to find failed tests' logs in the GitHub workflow
489
- . ci/run-build-and-tests: take a more high-level view
490
- . ci: fix code style
694
+ - ci: call `finalize_test_case_output` a little later
695
+ - ci: use `--github-workflow-markup` in the GitHub workflow
696
+ - ci: optionally mark up output in the GitHub workflow
697
+ - test(junit): avoid line feeds in XML attributes
698
+ - tests: refactor --write-junit-xml code
699
+ - ci/run-build-and-tests: add some structure to the GitHub workflow output
700
+ - ci: make it easier to find failed tests' logs in the GitHub workflow
701
+ - ci/run-build-and-tests: take a more high-level view
702
+ - ci: fix code style
703
704
Update the GitHub workflow support to make it quicker to get to the
705
failing test.
706
495
- Waiting for discussion to settle.
496
- cf. <220309.86tuc6lwpj.gmgdl@evledraar.gmail.com>
497
- cf. <220302.86mti87cj2.gmgdl@evledraar.gmail.com>
498
- cf. <30dbc8fb-a1db-05bc-3dcb-070e11cf4715@gmail.com>
707
+ Expecting a reroll.
708
+ cf. <52382f7c-5b6a-63b6-2eb2-26c12f31f529@gmail.com>
709
source: <pull.1117.v2.git.1646130289.gitgitgadget@gmail.com>
710
711
@@ -510,17 +720,14 @@ Release tarballs are available at:
720
source: <20220217225408.GB7@edef91d97c94>
721
722
513
-* tk/simple-autosetupmerge (2022-02-25) 2 commits
514
- - t3200: tests for new branch.autosetupmerge option "simple"
723
+* tk/simple-autosetupmerge (2022-04-22) 1 commit
724
- merge: new autosetupmerge option 'simple' for matching branches
725
726
"git -c branch.autosetupmerge=simple branch $A $B" will set the $B
727
as $A's upstream only when $A and $B shares the same name, and "git
728
-c push.default=simple" on branch $A would push to update the
729
branch $A at the remote $B came from.
521
-
522
- Needs review.
523
- source: <pull.1161.v2.git.1645815142.gitgitgadget@gmail.com>
730
+ source: <pull.1161.v4.git.1647843442911.gitgitgadget@gmail.com>
731
732
733
* tk/untracked-cache-with-uall (2022-04-01) 2 commits
@@ -536,7 +743,8 @@ Release tarballs are available at:
743
source: <pull.985.v6.git.1648742535.gitgitgadget@gmail.com>
744
745
539
-* jh/builtin-fsmonitor-part3 (2022-03-25) 28 commits
746
+* jh/builtin-fsmonitor-part3 (2022-04-22) 29 commits
747
+ - fsmonitor--daemon: allow --super-prefix argument
748
- t7527: test Unicode NFC/NFD handling on MacOS
749
- t/lib-unicode-nfc-nfd: helper prereqs for testing unicode nfc/nfd
750
- fsmonitor: on macOS also emit NFC spelling for NFD pathname
@@ -567,7 +775,7 @@ Release tarballs are available at:
775
- Merge branch 'jh/builtin-fsmonitor-part2' into jh/builtin-fsmonitor-part3
776
777
More fsmonitor--daemon.
570
- source: <pull.1143.v4.git.1648140680.gitgitgadget@gmail.com>
778
+ source: <pull.1143.v6.git.1650662994.gitgitgadget@gmail.com>
779
780
781
* js/bisect-in-c (2022-02-23) 14 commits