git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Avery Pennarun <apenwarr@gmail.com>,
	Git Mailing List <git@vger.kernel.org>,
	Mihai Sucan <mihai.sucan@gmail.com>
Subject: Re: git svn errors out with git-cat-file "usage" message
Date: Thu, 30 Apr 2009 09:18:08 +0200	[thread overview]
Message-ID: <46a038f90904300018u7101943blef084dc907a04c8d@mail.gmail.com> (raw)
In-Reply-To: <49F8C127.4000400@drmicha.warpmail.net>

On Wed, Apr 29, 2009 at 11:05 PM, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
> But I just re-read your original report, and there's some inconsistency:
>
> git-svn triggers cat-file's usage message which says "git-cat-file ...".
> The dash indicates that it is a git cat-file before v1.6.0.1-13-g34baebc
> (where the dash was removed), so it's definitely not the current maint
> you think you are using.
>
> Do you have older ubuntu git packages installed in $PATH?

Bingo! Yes,

~$ which git-cat-file
/usr/bin/git-cat-file
~$ /usr/bin/git version
git version 1.5.6.3

now that's really weird. git from ~/bin is using git-cat-file from
/usr/bin instead of ~/libexec/git-core ... how is the libexec path set
in the PATH during the execution of the script?

the funny thing is that Ubuntu wants to have git-core in place if
you're rebuilding kernel packages. I don't need to rebuild my kernel
anymore but I am sure this is an issue for others. What's the trick?
Add the libexec/git-core to the PATH before /usr/bin? Should git
internally append libexec/git-core earlier in the search path?

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

  reply	other threads:[~2009-04-30  7:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29 15:11 git svn errors out with git-cat-file "usage" message Martin Langhoff
2009-04-29 18:50 ` Avery Pennarun
2009-04-29 20:25   ` Michael J Gruber
2009-04-29 20:47     ` Martin Langhoff
2009-04-29 21:05       ` Michael J Gruber
2009-04-30  7:18         ` Martin Langhoff [this message]
2009-04-30  7:53           ` Michael J Gruber
2009-04-30  8:26           ` Andreas Ericsson
2009-04-30  8:46             ` Michael J Gruber
2009-04-30  8:53           ` Martin Langhoff
2009-04-30  9:28             ` Michael J Gruber
2009-04-30  9:42               ` Martin Langhoff
2009-04-30 14:41             ` Avery Pennarun
2009-04-30 15:03               ` Martin Langhoff
2009-04-30 16:26                 ` Avery Pennarun
2009-04-30 16:31                   ` Martin Langhoff
2009-04-30 16:49                     ` Michael J Gruber

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=46a038f90904300018u7101943blef084dc907a04c8d@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=apenwarr@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=mihai.sucan@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).