git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Robert Irelan <rirelan@epic.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: "git commit" fails due to spurious file in index
Date: Mon, 4 Mar 2013 21:58:58 +0100	[thread overview]
Message-ID: <87y5e2op9p.fsf@pctrast.inf.ethz.ch> (raw)
In-Reply-To: <2D9BD788B02ABA478C57929170AF952B7622B5@EXCH-MBX-3.epic.com> (Robert Irelan's message of "Mon, 4 Mar 2013 18:15:36 +0000")

Robert Irelan <rirelan@epic.com> writes:

> Now, when I run 'git add admin_script/setup' to add the new directory to
> the repo and then try to commit, I receive the following message:
>
>     $ git commit
>     mv: cannot stat `admin_scripts/setup/2012/setup': No such file or directory
>
> The error message is correct in that `admin_scripts/setup/2012/setup`
> does not exist, either as a file or as a directory. However, I'm not
> attempting to add this path at all. Using grep, I've confirmed that the
> only place this path appears in any of my files is in `.git/index`.

To me that sounds like the message comes from a commit hook.  Can you
check if you have anything in .git/hooks/, especially pre-commit?

There really isn't any other good reason why 'git commit' would call
'mv' (plain mv, not git!).

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  reply	other threads:[~2013-03-04 20:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04 18:15 "git commit" fails due to spurious file in index Robert Irelan
2013-03-04 20:58 ` Thomas Rast [this message]
2013-03-05 15:30   ` Robert Irelan
2013-03-05 10:40 ` Torsten Bögershausen
2013-03-05 15:30   ` Robert Irelan

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=87y5e2op9p.fsf@pctrast.inf.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=git@vger.kernel.org \
    --cc=rirelan@epic.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.
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).