Fatal: Could not fetch refs from userid@domain:project/gitrepo

[GoogleCodeExporter]

What steps will reproduce the problem?
1. I just use any account and create new project
2. Then create new repository in the project (no README, gitignore) e.q. no 
initial commit
3. If I try to clone 2.'s repository then i can show the error message like 
title

What is the expected output? What do you see instead?
Before::
fatal: could not fetch refs from ????@localhost:????/????
After::
warning: You appear to have cloned an empty repository. (like github)
or
warning: remote HEAD refers to nonexistent ref, unable to checkout.

AND I want get empty repository in my local working dir when I clone empty 
remote git repository.

What version of the product are you using? On what operating system?
OS: Windows 7
Version: Github Src clone -> I want to use server side with it

Please provide any additional information below.
Please contact (reply) with "oh4851@gmail.com" as soon as possible

Original issue reported on code.google.com by oh4...@gmail.com on 26 Jan 2015 at 6:52

[GoogleCodeExporter]

Git should clone an empty repository just fine.  The error messages you see are 
standard git client error messages when cloning an empty repo.

I'm not sure what problem you are reporting here.

Original comment by James.Mo...@gmail.com on 26 Jan 2015 at 3:06

[GoogleCodeExporter]

I got the same issue like
http://stackoverflow.com/questions/24113420/fail-to-clone-repository-using-ssh-o
n-gitblit

if i try to clone not empty repository, then no problem.
but, i try on empty repository with ssh protocol i got the fatal error.

Original comment by oh4...@gmail.com on 27 Jan 2015 at 12:58

[GoogleCodeExporter]

I'm not totally sure where the problem lies: Gitblit or JGit.

There are two other solutions I'm sure you are aware of:

1. Initialize the repo with a README or gitignore or whatever through the web 
ui.
2. Init a local repo, set the remote to your empty repository, and push.

I think I saw you post to the JGit mailing list about this issue.  I can't 
recall if they said this was a bug in JGit - seems like I remember that.

Are you interested in proposing a PR that resolves the issue?

Original comment by James.Mo...@gmail.com on 26 Feb 2015 at 3:12