fatal: protocol error: expected sha/ref
Dear Lennart,
You should probably know that typing the correct URL would work better for cloning a bzr branch (yes a branch, not a repository).
This is what I get when I try to feed git a random invalid URL:
$ git clone git://github.com/idontexist
Initialized empty Git repository in /home/asabil/Desktop/idontexist/.git/
fatal: protocol error: expected sha/ref, got ‘
*********’No matching repositories found.
*********’
Now is probably the time to stop this non constructive “my DVCS is better than yours”, and focus on writing code and fixing bugs.
Categories: Uncategorized
It’s Lennart, not Lenart.
I’m sorry, is git clone’s output not clear enough or what seems to be the complaint? If you specify it I can fix it in a couple of minutes.
Thanks for the input, I fixed Lennart’s name in the post.
Otherwise, I really don’t care about git’s output message, I was just replying to Lennart’s spreading uninformed nonsense about bzr.
this isn’t uninformed nonsense, lennart’s bzr error message doesn’t state what’s going on (the repository doesn’t exists there), whereas your’s git error message clearly say there’s “no matching repository” here. a random DVCS user, would probably understand the later better than the former.
while git has some progress to make with some error message, bzr definitely has too.
Well, the issue is that you are assuming that “repository” belongs to the bzr vocabulary, and actually it doesn’t, there is no such thing as a repository (in the way you intend it) in bzr, actually everything is a branch, and you clone branches not repositories.
The error message you are suggesting just doesn’t make any sense in the context of the bzr terminology.
Kick-ass post, amazing looking website, added it to my favorites.