From: Michael J Gruber <git@drmicha.warpmail.net>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Strangely hosed git install
Date: Thu, 28 May 2009 11:47:40 +0200 [thread overview]
Message-ID: <4A1E5DBC.2090908@drmicha.warpmail.net> (raw)
In-Reply-To: <46a038f90905280234h35b9b90fwfc52434cd056578e@mail.gmail.com>
Martin Langhoff venit, vidit, dixit 28.05.2009 11:34:
> On Thu, May 28, 2009 at 10:29 AM, Michael J Gruber
> <git@drmicha.warpmail.net> 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
next prev parent reply other threads:[~2009-05-28 9:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 7:08 Strangely hosed git install Martin Langhoff
2009-05-28 7:18 ` Junio C Hamano
2009-05-28 7:22 ` Martin Langhoff
2009-05-28 8:29 ` Michael J Gruber
2009-05-28 9:34 ` Martin Langhoff
2009-05-28 9:39 ` Martin Langhoff
2009-05-28 9:47 ` Michael J Gruber [this message]
2009-05-28 10:11 ` Martin Langhoff
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=4A1E5DBC.2090908@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=martin.langhoff@gmail.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).