Skip to content

git status returns different results when core.fscache enabled #679

@latkin

Description

@latkin
  • I was not able to find an open
    or closed issue
    matching what I'm seeing

Setup

Win10, x64
git version 2.6.3.windows.1
Default install as far as I recall
Problem repros in all shells

Details

  • Clone https://github.com/latkin/filetest
    • foo:bar file has invalid Windows filename. It is copied as size-0 file foo.
    • Add foo to gitignore
  • With core.fscache false, working directory is shown as clean by git status
  • With core.fscache true, file foo:bar is flagged with deleted status.

Expected: Working directory status is reported the same with/without core.fscache, in all cases.

Motivation: I work on windows but most of my team is on OSX. They put files named like foo:bar in the repo. I can happily ignore them with a private gitignore when core.fscache is turned off, but they pollute my working directory when I try to use core.fscache true (which I'd like to do for perf reasons).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions