Re: [PATCH v1 1/1] test: Correct detection of UTF8_NFD_TO_NFC for APFS

On Mon, Apr 30, 2018 at 8:41 AM, Torsten Bögershausen wrote: > On 30.04.18 17:33, Elijah Newren wrote: > >> On Sun, Apr 29, 2018 at 11:35 PM, wrote: >>> From: Torsten Bögershausen >>> >>> @@ -1106,12 +1106,7 @@ test_lazy_prereq UTF8_NFD_TO_NFC ' >>

Re: [PATCH v1 1/1] test: Correct detection of UTF8_NFD_TO_NFC for APFS

On 30.04.18 17:33, Elijah Newren wrote: > Hi, > > On Sun, Apr 29, 2018 at 11:35 PM, wrote: >> From: Torsten Bögershausen >> >> On HFS (which is the default Mac filesystem prior to High Sierra), >> unicode names are "decomposed" before recording. >> On APFS, which

Re: [PATCH v1 1/1] test: Correct detection of UTF8_NFD_TO_NFC for APFS

Hi, On Sun, Apr 29, 2018 at 11:35 PM, wrote: > From: Torsten Bögershausen > > On HFS (which is the default Mac filesystem prior to High Sierra), > unicode names are "decomposed" before recording. > On APFS, which appears to be the new default filesystem in Mac OS

Re: [PATCH v1 1/1] test: Correct detection of UTF8_NFD_TO_NFC for APFS

On 30.04.18 09:56, Junio C Hamano wrote: > tbo...@web.de writes: > >> From: Torsten Bögershausen >> >> On HFS (which is the default Mac filesystem prior to High Sierra), >> unicode names are "decomposed" before recording. >> On APFS, which appears to be the new default filesystem

Re: [PATCH v1 1/1] test: Correct detection of UTF8_NFD_TO_NFC for APFS

tbo...@web.de writes: > From: Torsten Bögershausen > > On HFS (which is the default Mac filesystem prior to High Sierra), > unicode names are "decomposed" before recording. > On APFS, which appears to be the new default filesystem in Mac OS High > Sierra, filenames are recorded as