Martin Langhoff venit, vidit, dixit 28.05.2009 11:34: > On Thu, May 28, 2009 at 10:29 AM, Michael J Gruber > <git@xxxxxxxxxxxxxxxxxxxx> wrote: >> Yes, but your shell seems to find git-diff somewhere, so what about: >> >> type --all git-diff >> echo $PATH > > $ type --all git-diff > bash: type: git-diff: not found > $ echo $PATH > /home/martin/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games > > there is _no other_ git-diff. It's bash magic. See > http://popey.com/command_not_found This is insane. Don't they even distinguish between an interactive shell and a non-interactive one? > > Note that all the key commands work. I clone, diff, commit, push, > merge daily on this machine. > >> OTOH: The git-pack-objects usage line indicates that you clearly have >> older plumbing lying around. I suspect there are at least 2 issues on >> that box. > > Might be. Maybe ~/bin got cleaned up but not libexec? Or the bisecting > back-and-forth left stray bits in ~/bin? Well, I would say go "find / git-diff-index", or simply nuke anything git you find and do a clean install... "find"ing the left over bits would help making sure that git's own search path is OK. Michael -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html