problems with cloning; http vs git protocols?

["A.J. Rossini" <blindglobe@gmail.com>]

Greetings -

I've been working on a project that I'm finally making available to
others, and have set it up on repo.or.cz.

It originated as an SVN project on a private repository, and I've been
using git-svn for communication with the original repo.

After having pushed it up

( git push -v git+ssh://repo.or.cz/srv/git/rclg.git master:master
tonylocal:tonylocal )

I've been working to verify it to write instructions for friends, and
here is the basic problem:

 git clone http://repo.or.cz/w/rclg.git

fails:
$ cd /tmp
$ git clone http://repo.or.cz/w/rclg.git/
Initialized empty Git repository in /tmp/rclg/.git/
/usr/bin/git-clone: line 381: cd: /tmp/rclg/.git/refs/remotes/origin:
No such file or directory
fatal: Not a valid object name HEAD

but

 git clone git://repo.or.cz/rclg.git

works:
$ rm -rf rclg
$ git clone git://repo.or.cz/rclg.git
Initialized empty Git repository in /tmp/rclg/.git/
remote: Generating pack...
remote: Done counting 446 objects.
remote: Deltifying 446 objects...
remote:  100% (446/446) done
Indexing 446 objects...
remote: Total 446 (delta 239), reused 446 (delta 239)
 100% (446/446) done
Resolving 239 deltas...
 100% (239/239) done



?? Is there something I'm doing wrong with the push statement, or with
my git-svn work, or is it a bug, or have I just forgotten/misread a
step??

(I'd like to get http working for a few corporate firewall-hindered friends).

best,
-tony

blindglobe@gmail.com
Muttenz, Switzerland.
"Commit early,commit often, and commit in a repository from which we
can easily roll-back your mistakes" (AJR, 4Jan05).