[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 10:55:16 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 |
On 17/05/15 00:34, Jim Meyering wrote:
> I noticed that since the addition of the file,
> tests/tail-2/F-vs-rename.sh, one can no longer
> clone coreutils onto a case-challenged file system,
> because there is also a file in that directory whose
> name differs only in the case of the "f":
>
> tests/tail-2/f-vs-rename.sh
>
> What do you think about fixing this?
> Since it's easy to avoid, you may want to write a
> syntax-check rule using something like this:
>
> $ git ls-files|tr '[:upper:]' '[:lower:]'|sort|uniq -d
> tests/tail-2/f-vs-rename.sh
>
> Actual consequence?
> When I clone onto an hfs file system (OS/X), the initial
> is shown as unclean, with tests/tail-2/F-vs-rename.sh
> being shown as modified (with the differences to transform
> it to the contents of the lower-case-named file).
Yes it's definitely worth avoiding that issue.
Proposed patch attached.
thanks!
Pádraig
case-insens.patch
Description: Text Data