From: Antony Stubbs <antony.stubbs@gmail.com>
To: Jeff King <peff@peff.net>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: cvs import and internal plumbing commands
Date: Sat, 18 Jul 2009 09:44:08 +1200 [thread overview]
Message-ID: <7590CBC0-25BA-41D4-9BB5-40550A6CDDF6@gmail.com> (raw)
In-Reply-To: <20090716100121.GA6742@coredump.intra.peff.net>
On 16/07/2009, at 10:01 PM, Jeff King <peff@peff.net> wrote:
> On Sun, Jul 05, 2009 at 02:43:01PM +1200, Antony Stubbs wrote:
>
>> I've got a new install from mac-ports and am having trouble with cvs
>> import not finding the plumbing commands.
>>
>> It seems that cvsimport still uses all the old style git-hash-object
>> type commands, instead of the new " git hash-object" command style.
>> And on my system, I don't have any of the old style commands.
>
> The old style commands should be in the execdir (e.g.,
> /usr/local/libexec/git-core). That directory should be placed at the
> beginning of the PATH when you run "git cvsimport".
>
> If you run "git --exec-path", what directory does it print? If you
> go to
> that directory, is it filled with dashed git commands?
>
> -Peff
Ok cool, I'll have a look when I get home.
But should we not migrate it for the future anyway? An at least that
way it would work by default, in this environment?
Cheers,
Antony
www.sharca.com
next prev parent reply other threads:[~2009-07-17 21:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-05 2:43 cvs import and internal plumbing commands Antony Stubbs
2009-07-05 6:28 ` Antony Stubbs
2009-07-06 12:15 ` [PATCH 1/1] " astubbs
2009-07-16 10:01 ` Jeff King
2009-07-17 21:44 ` Antony Stubbs [this message]
2009-07-17 21:45 ` Jeff King
2009-07-17 21:59 ` Antony Stubbs
2009-07-19 23:57 ` [PATCH] " Antony Stubbs
2009-07-20 2:43 ` Junio C Hamano
2009-07-20 15:34 ` Jeff King
2009-07-21 23:24 ` Antony Stubbs
2009-07-22 0:43 ` Junio C Hamano
2009-07-22 2:59 ` Jeff King
2009-07-22 3:06 ` Junio C Hamano
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=7590CBC0-25BA-41D4-9BB5-40550A6CDDF6@gmail.com \
--to=antony.stubbs@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).