Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Sat, 26 Dec 2020 23:08:03 +0000
From:   Al Viro <viro@zeniv.linux.org.uk>
To:     Theodore Dubois <tblodt@icloud.com>
Cc:     linux-kernel@vger.kernel.org
Subject: Re: linux.git is broken on a case-insensitive filesystem
Message-ID: <20201226230803.GC3579531@ZenIV.linux.org.uk>
References: <080A3B31-608F-4A36-A5DE-B75670D2452E@icloud.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <080A3B31-608F-4A36-A5DE-B75670D2452E@icloud.com>
Sender: Al Viro <viro@ftp.linux.org.uk>
Precedence: bulk

On Sat, Dec 26, 2020 at 02:30:13PM -0800, Theodore Dubois wrote:
> I'm currently hacking on Linux trying to run a sort of UML-style thing on macOS (please don't question my sanity :), and I've run into various issues stemming from macOS having a case-insensitive filesystem. 
> 
> The one you run into immediately is: there are a number of files (mostly in netfilter) that have different uppercase and lowercase versions. net/netfilter/xt_DSCP.c and net/netfilter/xt_dscp.c are quite different. Last I checked, git would pseudo-randomly pick one of these to check out, and then show the other one as having unstaged changes making it look like the first one. This causes problems when switching branches. I've worked around this with a sparse checkout that excludes these files, but it's not great.
> 
> The gitignore also contains the pattern *.s, which excludes *.S as well when git is ignoring case.
> 
> Is there any interest in fixing these?

<wry> Just how could we fix a long-standing design flaw in macOS? </wry>