Status shows untracked directory without any untracked file in it

How that is possible? Is it a bug?

alexko@ALEXKO-LAB b:\ » git status --untracked-files=normal # On branch master # Untracked files: # (use "git add <file>..." to include in what will be committed) # # data/fex/lba/hi/qna/ nothing added to commit but untracked files present (use "git add" to track)

alexko@ALEXKO-LAB b:\ » git status --untracked-files=all # On branch master nothing to commit (working directory clean)

-- Alexander Kostikov

On Thu, Apr 05, 2012 at 10:19:00PM -0700, Alexander Kostikov wrote:

Maybe. What git version and what platform are you on? There was a bug in versions of git earlier than v1.7.8 that showed the symptom you describe on case-insensitive filesystems. It was fixed by commit 2548183, which contains more details.

-Peff

Am 06.04.2012 07:19, schrieb Alexander Kostikov:

I don't think so. git status normally does not look inside directories that do not contain any tracked files.

Here, git status only knows that it does not track anything inside .../qna/, and it tells you that it found this directory.

Here, you ask to list files in all directories, but, alas, the directory does not contain anything untracked. The directory itself is not listed, because git would be unable to track an empty directory.

-- Hannes

On Fri, Apr 06, 2012 at 08:58:03PM +0200, Johannes Sixt wrote:

I think it does:

  $ git init tmp && cd tmp
  $ echo content >tracked
  $ git add tracked
  $ mkdir untracked

  $ git status --untracked-files=normal
  # On branch master
  #
  # Initial commit
  #
  # Changes to be committed:
  #       new file:   tracked
  #

  $ >untracked/file
  $ git status --untracked-files=normal
  # On branch master
  #
  # Initial commit
  #
  # Changes to be committed:
  #       new file:   tracked
  #
  # Untracked files:
  #       untracked/

-Peff

[Please keep replies on the list, so others can benefit from the
 discussion. And please don't top-post.]

On Fri, Apr 06, 2012 at 09:30:20AM -0700, Alexander Kostikov wrote:

Your version should have the fix, so it may be a new issue. Is it easily reproducible? Can you share a short reproduction recipe, or possibly share the repo showing the problem?

-Peff