git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: seanh <snhmnd@gmail.com>
To: Shaun Ruffell <sruffell@digium.com>
Cc: git@vger.kernel.org
Subject: Re: Files that cannot be added to the index
Date: Sat, 27 Aug 2011 17:35:36 +0200	[thread overview]
Message-ID: <20110827153536.GA291@sooty-2.local> (raw)
In-Reply-To: <20110826211233.GB3093@digium.com>

On Fri, Aug 26, 2011 at 04:12:33PM -0500, Shaun Ruffell wrote:
> Not sure if this is your problem exactly but awhile back I ran into
> something similar to what you describe and tracked it down to the
> fact that my filesystem was case insensitive. i.e.

My filesystem (HFS+ on OSX Lion) is case-insensitive, yeah. I bet you're
right, because in one repo the modified file shows up in `git status` as
LOG.txt but in the output from `ls` it is called `Log.txt`. It's the
same in the other repo that has the problem, the case of the filename
that is having the problem is different in `git status` and `ls`.

Perhaps the problem might have been introduced by moving the repo from a
case-sensitive to an insensitive filesystem? Or by originally starting
the repo on a sensitive fs and then using git clone to clone it onto an
insensitive one. Or, maybe at some point I committed a change to the
case of the filename and that introduced a problem on case-insenstive
filesystems.

Did you find a way around the problem? I guess that the repo does not
really have any uncommitted changes, so I just want to convince `git
status` and `git diff` of this.

  parent reply	other threads:[~2011-08-27 15:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-26 12:26 Files that cannot be added to the index seanh
2011-08-26 14:10 ` Michael J Gruber
2011-08-26 20:59   ` seanh
2011-08-26 21:12     ` Shaun Ruffell
2011-08-27  6:07       ` Jeff King
2011-08-27 15:39         ` seanh
2011-08-27 18:40         ` Shaun Ruffell
2011-08-27 19:26           ` Shaun Ruffell
2011-08-27 15:35       ` seanh [this message]
2011-08-27 21:44         ` seanh

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=20110827153536.GA291@sooty-2.local \
    --to=snhmnd@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sruffell@digium.com \
    /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).