[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: compromise for case-challenged file systems?
From: |
Pádraig Brady |
Subject: |
Re: compromise for case-challenged file systems? |
Date: |
Sun, 17 May 2015 23:42:33 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 |
On 17/05/15 23:16, Jim Meyering wrote:
> On Sun, May 17, 2015 at 7:48 AM, Pádraig Brady <address@hidden> wrote:
>> -sc_case_insensitive_file_names:
>> - @git ls-files | sort -f | $(srcdir)/src/uniq -Di | grep . && \
>> +sc_case_insensitive_file_names: src/uniq
>> + @git ls-files | sort -f | src/uniq -Di | grep . && \
>
> Looks good. Thanks!
> Is there a reason not to prefix "sort" as "src/sort", as is done with uniq?
Well sort -f is standardized, and using the systems sort
avoids the need for an explicit dependency on src/sort.
There are issues with the specific orders of some versions of sort,
though uniq only cares that matching items are together,
so doesn't matter in this case.
cheers,
Pádraig.