On Mon, Oct 17, 2016 at 3:57 PM, Johannes Schindelin
<johannes.schinde...@gmx.de> wrote:
> Hi Stefan,
> On Sun, 16 Oct 2016, Stefan Beller wrote:
>> Conceptually I would prefer if we had a single switch that indicates a
>> case insensitive FS.
> AFAIU Lars' use case is where the FS is *case sensitive*, but he still
> needs the .gitattributes to be *case insensitive* because that file
> originates from a developer with such a file system.
> Otherwise he would simply tack onto the core.ignoreCase flag.

That sounds to me like setting core.ignoreCase to true (on all devs'
repo) would "solve" this. Yes core.ignoreCase may introduce some side
effects when used on case-sensitive filesystems, so we probably want
something in the same spirit but limited to .gitattributes and
.gitignore only.

Reply via email to