Re: [PATCH v2] git prompt: Use toplevel to find untracked files.

From: Cody Taylor <cody.taylor@maternityneighborhood.com>
Date: Mar 16, 2015, 00:54 UTC
Message-ID: <CAHWMk2aq7dW5nBW1f8T4TWfRC70hp-6kR5P79m_E4zccuy53aA@mail.gmail.com>

SZEDER Gábor <szeder@ira.uka.de> writes:

> Somehow I had a hard time making sense out of "when the current working
> directory was not a parent of the untracked file".  Perhaps "when the
> untracked files are outside of the current working directory" would be
> easier to grok?

That description doesn't cover all cases.

Scenario #1: Let's say there is an untracked file at `$ROOT/file`. When your CWD is `$ROOT/`, all is well. If you cd to `$ROOT/src/` the ls-files command failed to find the untracked file.

Scenario #2: Let's say there is an untracked file at `$ROOT/src/file`. The ls-files command would find the file if the CWD is `$ROOT/` or `$ROOT/src/`, but not if the CWD is `$ROOT/bin/` or `$ROOT/src/folder/`.

Your description may be easier to understand, but I don't agree it's accurate.