From: David Miller <davem@davemloft.net>
To: git@vger.kernel.org
Subject: git-ls-files prefix superset problem
Date: Mon, 31 Jul 2006 22:13:27 -0700 (PDT) [thread overview]
Message-ID: <20060731.221327.26966465.davem@davemloft.net> (raw)
I had been previously using git-1.1.3 on my local repositories
and I upgraded to the current git head:
b63fafdfd844c2037fba53b9944431c1378b4135
git commit stopped working, specifically it dies on
git-ls-files:
davem@sunset:~/src/GIT/net-2.6$ ../git/git-ls-files -- net/ipv4/tcp.c
fatal: git-ls-files: internal error - cache entry not superset of prefix
davem@sunset:~/src/GIT/net-2.6$
I added some debugging:
Trying get_pathspec([(null)],[net/ipv4/tcp.c])
prefixlen(0)
prefix_path() gives [net/ipv4/tcp.c]
ERROR: pathspec(net/ipv4/tcp.c)
verify_pathspec: len(9)
ERROR: len(9) ce_namelen(ce)(7) ce->name(COPYING)
Is something wrong with my index file?
I tried to rebuild it using:
git read-tree master
git checkout-index -f -a
git update-index --refresh
but I keep getting the same problem.
It happens on all of my local 2.6.x kernel GIT trees.
Any ideas?
Thanks a lot.
next reply other threads:[~2006-08-01 5:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 5:13 David Miller [this message]
2006-08-01 5:18 ` git-ls-files prefix superset problem Linus Torvalds
2006-08-01 5:25 ` David Miller
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=20060731.221327.26966465.davem@davemloft.net \
--to=davem@davemloft.net \
--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