From: Shaun Ruffell <sruffell@digium.com>
To: git@vger.kernel.org
Subject: Re: Files that cannot be added to the index
Date: Fri, 26 Aug 2011 16:12:33 -0500 [thread overview]
Message-ID: <20110826211233.GB3093@digium.com> (raw)
In-Reply-To: <20110826205919.GB8107@sooty-2.local>
On Fri, Aug 26, 2011 at 10:59:19PM +0200, seanh wrote:
> I'm using git version 1.7.4.4 on OSX Lion, from macports. (I was
> having the problem on Snow Leopard too.)
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.
$ git clone git://github.com/sruffell/dahdi-linux
Cloning into dahdi-linux...
done.
$ cd dahdi-linux/
$ ls
LICENSE Makefile UPGRADE.txt drivers
LICENSE.LGPL README build_tools include
$ git ls-files -m
$ rm Makefile
$ touch makefile
$ git add makefile
$ git ls-files -m
Makefile
$ git commit
# On branch master
# Changes not staged for commit:
# (use "git add <file>..." to update what will be committed)
# (use "git checkout -- <file>..." to discard changes in working directory)
#
# modified: Makefile
#
no changes added to commit (use "git add" and/or "git commit -a")
$ git add makefile
$ git commit
# On branch master
# Changes not staged for commit:
# (use "git add <file>..." to update what will be committed)
# (use "git checkout -- <file>..." to discard changes in working directory)
#
# modified: Makefile
#
no changes added to commit (use "git add" and/or "git commit -a")
next prev parent reply other threads:[~2011-08-26 21:12 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110826211233.GB3093@digium.com \
--to=sruffell@digium.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).