git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: Alexander Kostikov <alex.kostikov@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Status shows untracked directory without any untracked file in it
Date: Fri, 06 Apr 2012 20:58:03 +0200	[thread overview]
Message-ID: <4F7F3CBB.8030805@kdbg.org> (raw)
In-Reply-To: <CAGAhT3n3hHV+UhT+D1o60OAS23WFmx+Lxg=aqYMGC=U-LR1QUA@mail.gmail.com>

Am 06.04.2012 07:19, schrieb Alexander Kostikov:
> How that is possible? Is it a bug?

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

> 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)

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

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

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

  parent reply	other threads:[~2012-04-06 18:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06  5:19 Status shows untracked directory without any untracked file in it Alexander Kostikov
2012-04-06  6:14 ` Jeff King
     [not found]   ` <CAGAhT3nmOtZLusT8DXy9iWQsNkH2Pqc3YCf-22FZJ-fhHf38cw@mail.gmail.com>
2012-04-06 22:04     ` Jeff King
2012-04-06 18:58 ` Johannes Sixt [this message]
2012-04-06 21:59   ` Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F7F3CBB.8030805@kdbg.org \
    --to=j6t@kdbg.org \
    --cc=alex.kostikov@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).