From: Andrey Kiyanovsky <andrey.kiyanovsky@gmail.com>
To: git@vger.kernel.org
Subject: Git status reports untracked on tracked files
Date: Wed, 29 May 2013 11:40:56 +0300 [thread overview]
Message-ID: <CAO-zUnh4018FSnsXzX4gLw-4AnWsKgEiZ5P4pktjxNokargQwA@mail.gmail.com> (raw)
I would be grateful for any thoughts about the follow problem.
Git status reports untracked files:
$ git status
# On branch master
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# resource.enlighten/map/enlighten_test/.enlighten/__build_object__/geometry/land_9/processed/
nothing added to commit but untracked files present (use "git add" to track)
But we have files at this directory at index:
$ git ls-tree -r HEAD |grep land_9/processed/root.pim
100644 blob 9eeca5c75dc2c945600b6e0d253a8cb8191b7e80
resource.enlighten/map/enlighten_test/.enlighten/__build_object__/geometry/land_9/processed/root.pim
I have checked this error appear after the first commit, that added this file.
I have tried:
1. Clone repo.
2. Clean/Checkout file (as described at this [1] article) - after
checkout status is untracked.
3. Copy full directory resource.enlighten/ to another repo and add
commit - no errors.
4. Run git fsck - no errors.
Git version 1.8.1.2. for Windows
Git config:
[core]
repositoryformatversion = 0
filemode = false
bare = false
logallrefupdates = true
symlinks = false
ignorecase = true
hideDotFiles = dotGitOnly
compression = 1
Thank you in advance.
[1] http://stackoverflow.com/questions/11525358/git-untracked-files-list-is-wrong
next reply other threads:[~2013-05-29 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 8:40 Andrey Kiyanovsky [this message]
2013-06-03 22:26 ` Git status reports untracked on tracked files Jeff King
2013-06-04 9:05 ` Andrey Kiyanovsky
2013-06-04 16:39 ` Karsten Blees
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAO-zUnh4018FSnsXzX4gLw-4AnWsKgEiZ5P4pktjxNokargQwA@mail.gmail.com \
--to=andrey.kiyanovsky@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).