From: Martin Langhoff <martin.langhoff@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
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 12:11:01 +0200 [thread overview]
Message-ID: <46a038f90905280311p406a528atb8d21a30fe53b0e3@mail.gmail.com> (raw)
In-Reply-To: <4A1E5DBC.2090908@drmicha.warpmail.net>
On Thu, May 28, 2009 at 11:47 AM, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
> This is insane. Don't they even distinguish between an interactive shell
> and a non-interactive one?
Yes they do. I mentioned it but I didn't think it was the reason
behind the problem.
> 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.
well, that's not what happens when people bisect back and forth. It
used to be reasonably safe, it got unsafe when we moved lots of things
to libexec (and therefore the make install target got a nice warning
message about it). Now there might something acting up again.
Alas, I didn't keep a backup of my libexec :-/
m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
prev parent reply other threads:[~2009-05-28 10:11 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
2009-05-28 10:11 ` Martin Langhoff [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=46a038f90905280311p406a528atb8d21a30fe53b0e3@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).