summaryrefslogtreecommitdiff
path: root/tests-clar/resources/merge-resolve/.gitted/refs/heads/trivial-5alt-1-branch
diff options
context:
space:
mode:
authorEdward Thomson <ethomson@edwardthomson.com>2018-01-21 14:00:50 +0000
committerEdward Thomson <ethomson@edwardthomson.com>2018-01-21 14:37:05 +0000
commit9af7fbc37d8a99cc58e9d890106644ad5c3ccdc7 (patch)
treecf3e13911a42de514eb2030300ed48c07c50381f /tests-clar/resources/merge-resolve/.gitted/refs/heads/trivial-5alt-1-branch
parent45f584090818c59ba27ca95b1e930a41c424d6f1 (diff)
downloadlibgit2-ethomson/apfs_precompose_fixes.tar.gz
status::renames: write NFD instead of NFC filenameethomson/apfs_precompose_fixes
Update the status::renames test to create an NFD format filename in the core.precomposedunicode tests. Previously, we would create an NFC format filename. This was to take advantage of HFS+ filesystems, which always use canonically decomposed formats, and would actually write the filename to disk as an NFD filename. So previously, we could create an NFC filename, but read it normally as an NFD filename. But APFS formats do not force canonically decomposed formats for filenames, so creating an NFC filename does not get converted to NFD. Instead, the filename will be written in NFC format. Our test, therefore, does not work - when we write an NFC filename, it will _remain_ NFC. Update the test to write NFD always. This will ensure that the file will actually be canonically decomposed on all platforms: HFS+, which forces NFD, and APFS, which does not. Thus, our test will continue to ensure that an NFD filename is canonically precomposed on all filesystems.
Diffstat (limited to 'tests-clar/resources/merge-resolve/.gitted/refs/heads/trivial-5alt-1-branch')
0 files changed, 0 insertions, 0 deletions