From: Martin Langhoff <martin.langhoff@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Strangely hosed git install
Date: Thu, 28 May 2009 09:22:13 +0200 [thread overview]
Message-ID: <46a038f90905280022s1c07565bnf26335fccf7c7e94@mail.gmail.com> (raw)
In-Reply-To: <7vprdthezg.fsf@alter.siamese.dyndns.org>
On Thu, May 28, 2009 at 9:18 AM, Junio C Hamano <gitster@pobox.com> wrote:
> "type --all git"?
> "git --exec-path"?
> "ls $(git --exec-path)"?
>
It all looks fairly correct to me:
$ type --all git
git is /home/martin/bin/git
$ git --exec-path
/home/martin/libexec/git-core
$ ls $(git --ex
ec-path)
git git-merge-index
git-add git-merge-octopus
git-add--interactive git-merge-one-file
git-am git-merge-ours
git-annotate git-merge-recursive
git-apply git-merge-resolve
git-archimport git-merge-stupid
git-archive git-merge-subtree
git-bisect git-mergetool
git-bisect--helper git-mergetool--lib
git-blame git-merge-tree
git-branch git-mktag
git-bundle git-mktree
git-cat-file git-mv
git-check-attr git-name-rev
git-checkout git-pack-objects
git-checkout-index git-pack-redundant
git-check-ref-format git-pack-refs
git-cherry git-parse-remote
git-cherry-pick git-patch-id
git-citool git-peek-remote
git-clean git-prune
git-clone git-prune-packed
git-commit git-pull
git-commit-tree git-push
git-config git-quiltimport
git-count-objects git-read-tree
git-cvsexportcommit git-rebase
git-cvsimport git-rebase--interactive
git-cvsserver git-receive-pack
git-daemon git-reflog
git-describe git-relink
git-diff git-remote
git-diff-files git-repack
git-diff-index git-repo-config
git-difftool git-request-pull
git-difftool--helper git-rerere
git-diff-tree git-reset
git-fast-export git-revert
git-fast-import git-rev-list
git-fetch git-rev-parse
git-fetch-pack git-rm
git-fetch--tool git-send-email
git-filter-branch git-send-pack
git-fmt-merge-msg git-shell
git-for-each-ref git-shortlog
git-format-patch git-show
git-fsck git-show-branch
git-fsck-objects git-show-index
git-gc git-show-ref
git-get-tar-commit-id git-sh-setup
git-grep git-stage
git-gui git-stash
git-gui--askpass git-status
git-hash-object git-stripspace
git-help git-submodule
git-help--browse git-svn
git-http-fetch git-symbolic-ref
git-http-push git-tag
git-imap-send git-tar-tree
git-index-pack git-unpack-file
git-init git-unpack-objects
git-init-db git-update-index
git-instaweb git-update-ref
git-log git-update-server-info
git-lost-found git-upload-archive
git-ls-files git-upload-pack
git-ls-remote git-var
git-ls-tree git-verify-pack
git-mailinfo git-verify-tag
git-mailsplit git-web--browse
git-merge git-whatchanged
git-merge-base git-write-tree
git-merge-file
cheers,
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
next prev parent reply other threads:[~2009-05-28 7:22 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 [this message]
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
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=46a038f90905280022s1c07565bnf26335fccf7c7e94@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--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).