From: Junio C Hamano <junkio@cox.net>
To: Zack Brown <zbrown@tumblerings.org>
Cc: git@vger.kernel.org
Subject: Re: cg-clone produces "___" file and no working tree
Date: Tue, 18 Apr 2006 23:53:38 -0700 [thread overview]
Message-ID: <7vd5feawel.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060419053640.GA16334@tumblerings.org> (Zack Brown's message of "Tue, 18 Apr 2006 22:36:40 -0700")
Zack Brown <zbrown@tumblerings.org> writes:
> What is going on? I'm completely unable to clone a repository.
I have no idea how cg-* is broken, so I'll let Pasky answer
that, but I suspect your git installation is broken.
> If I try
> "git clone rsync://rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/git.git",
> I get this error: "git: 'clone' is not a git-command", and it prints a usage
> page, but "clone" is listed on that usage page.
That sounds intersting. Although rsync is deprecated for a long
time and git:// is the preferred transport, I do not get "is not
a git-command" error. Are you installing things correctly?
For example, as the first paragraph of INSTALL says, if you
override prefix= from the make command line, you need to do so
consistently when you build and when you install.
What do these command say?
$ git --exec-path
$ ls -l "`git --exec-path`/git-clone"
next prev parent reply other threads:[~2006-04-19 6:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 5:36 cg-clone produces "___" file and no working tree Zack Brown
2006-04-19 6:53 ` Junio C Hamano [this message]
2006-04-19 14:16 ` Zack Brown
2006-04-19 9:49 ` Petr Baudis
2006-04-19 14:21 ` Zack Brown
2006-04-19 14:48 ` Petr Baudis
2006-04-20 16:49 ` Zack Brown
2006-04-20 17:36 ` Junio C Hamano
2006-04-20 20:08 ` Zack Brown
2006-04-20 20:17 ` Junio C Hamano
2006-04-20 20:19 ` Petr Baudis
2006-04-20 20:26 ` Junio C Hamano
2006-04-20 20:35 ` Petr Baudis
2006-04-20 20:23 ` Junio C Hamano
2006-04-20 21:34 ` Zack Brown
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=7vd5feawel.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=zbrown@tumblerings.org \
/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).