From: "Shawn O. Pearce" <spearce@spearce.org>
To: Andrew Vit <andrew@avit.ca>
Cc: git@vger.kernel.org
Subject: Re: Files that want to delete themselves
Date: Wed, 24 Sep 2008 11:05:47 -0700 [thread overview]
Message-ID: <20080924180547.GA3669@spearce.org> (raw)
In-Reply-To: <19654453.post@talk.nabble.com>
Andrew Vit <andrew@avit.ca> wrote:
>
> I have a Rails project that I'm managing with git and I have a strange
> problem with one of the plugin directories. Every time I do `git add .` it
> tries to delete itself... Any idea what might be happening?
>
> andrew$ git status
> # On branch master
> # Changes to be committed:
> # (use "git reset HEAD <file>..." to unstage)
> #
> # new file: vendor/plugins/restful_authentication
> # deleted: vendor/plugins/restful_authentication/CHANGELOG
> # deleted: vendor/plugins/restful_authentication/README.textile
> # deleted: vendor/plugins/restful_authentication/Rakefile
> # deleted: vendor/plugins/restful_authentication/TODO
Are you on a case-insensitive filesystem like HFS+?
Is it possible that restful_authentication exists as a file in
your working directory, but as a directory in Git, but with a
different case?
What does `git ls-tree HEAD:vendor/plugins` show you as the last
committed contents of vendor/plugins?
I'm a little stumped, but it sounds like the issues that have come
up before due to a case-insensitive filesystem.
--
Shawn.
prev parent reply other threads:[~2008-09-24 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 17:55 Files that want to delete themselves Andrew Vit
2008-09-24 18:04 ` Petr Baudis
2008-09-24 18:18 ` Andrew Vit
2008-09-24 18:05 ` Shawn O. Pearce [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=20080924180547.GA3669@spearce.org \
--to=spearce@spearce.org \
--cc=andrew@avit.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.