From: Karsten Blees <karsten.blees@gmail.com>
To: Andrey Kiyanovsky <andrey.kiyanovsky@gmail.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: Git status reports untracked on tracked files
Date: Tue, 04 Jun 2013 18:39:18 +0200 [thread overview]
Message-ID: <51AE1836.7060701@gmail.com> (raw)
In-Reply-To: <CAO-zUniGNqxLJ9JrRMtfGF7O52sQsrGBoh0HJf+zh0czwt7ETQ@mail.gmail.com>
Am 04.06.2013 11:05, schrieb Andrey Kiyanovsky:
> I have tried Git 1.8.3 for Windows. Case is fixed. Thank you very much!
>
> 2013/6/4 Jeff King <peff@peff.net>:
>> On Wed, May 29, 2013 at 11:40:56AM +0300, Andrey Kiyanovsky wrote:
>>
>>> 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
>>
>> In the past there have been some problems with status listings of
>> untracked files when core.ignorecase is in use. I fixed some cases with
>> a commit that went into v1.7.8, but some problems remained. Karsten
>> Blees (cc'd) did some work that went into git v1.8.1.6, but I do not
>> know off-hand if it would fix your case or not.
>>
Yep, the hash collision bug can definitely cause this with ignorecase=true, glad it helped.
Another case in which Git for Windows will report tracked files as untracked is if you upgrade from < 1.7.10 with non-ASCII file names in the repository. Particularly annoying are hyphens (\u00ad), which look just like ASCII minus (\u002d). See [1] for details.
[1] https://github.com/msysgit/msysgit/wiki/Git-for-Windows-Unicode-Support
prev parent reply other threads:[~2013-06-04 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 8:40 Git status reports untracked on tracked files Andrey Kiyanovsky
2013-06-03 22:26 ` Jeff King
2013-06-04 9:05 ` Andrey Kiyanovsky
2013-06-04 16:39 ` Karsten Blees [this message]
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=51AE1836.7060701@gmail.com \
--to=karsten.blees@gmail.com \
--cc=andrey.kiyanovsky@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).