Git clone, file verification phase skipped

Question

ubuntu@site3-user03 :/projects$ git clone git://git.alsa-project.org/alsa-driver.git 

. This led to the following conclusion

 Cloning into 'alsa-driver'... remote: Counting objects: 208801, done. remote: Compressing objects: 100% (41538/41538), done. remote: Total 208801 (delta 162528), reused 206283 (delta 160012) Receiving objects: 100% (208801/208801), 37.00 MiB | 1.53 MiB/s, done. Resolving deltas: 100% (162528/162528), done. Checking connectivity... done. ubuntu@site3-user03 :/projects$ 

However, for some unknown reason, the cloning process did not include the File Check: 100% (xyz / zyx) stage.
Typically, the cloning process involves checking the workspace. In the end, my private fork has an empty workspace, and I have to decide where to fork, which can be tricky.

 ubuntu@site3-user03 :/projects/alsa-driver$ git ls-remote origin a1c6fbc1a65d8a755425d0b56077868148512891 HEAD 1721fb542b00f1c7aebc923732068f403b6062ad refs/heads/build a1c6fbc1a65d8a755425d0b56077868148512891 refs/heads/master 71b3b2b41dfbdeda78e2e7b62fe2afa8b451fb6e refs/heads/mirror b044dfe04f636d87fd391b575ba41e495e68e973 refs/heads/release 6386d9e39e6f364698648f4e4741897f83b00121 refs/tags/build/v1.0.1 234b00ebe6e1513c3ce8cdd83999c255bd5516eb refs/tags/build/v1.0.10 f888eb06d4c7af89faa2f9dda189d488312ecb07 refs/tags/build/v1.0.10rc1 e4c4d1037521f536b79f8d145979ec869db353f9 refs/tags/build/v1.0.10rc2 .... many more tags 

I expect the clone to execute a statement based on the remote HEAD, which indicates a specific commit on the remote computer.
What is the possible reason for the exit phase was skipped?
During the cloning process, I created a small readme file in the workspace. However, this file remains unplayable until this point. The plan is not to track this file.
Can this file creation disrupt the cloning process, so it cannot include the checkout stage?

 ubuntu@site3-user03 :/projects$ git clone [e-mail] :alsa-driver.git alsa-driver Cloning into 'alsa-driver'... The authenticity of host 'git.alsa-project.org (77.48.224.243)' can't be established. RSA key fingerprint is f1:0e:a7:1f:bc:1b:9f:71:00:85:c9:4a:8a:d9:d6:33. Are you sure you want to continue connecting (yes/no)? no Host key verification failed. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. ubuntu@site3-user03 :/projects$ 

So, I interrupted it, because I had a simple cloning process, in addition, there was not the slightest idea about all the resulting effects, confirming the continuation of the failed host check.

 git help clone 

and the examples made there are used, among others, in URL format

  The following syntaxes may be used with them: · git://host.xz[:port]/path/to/repo.git/ · http[s]://host.xz[:port]/path/to/repo.git/ ... git clone git://git.kernel.org/pub/scm/.../linux.git my-linux git clone --reference /git/linux.git \ git://git.kernel.org/pub/scm/.../linux.git \ my-linux · Create a bare repository to publish your changes to the public: git clone --bare -l /home/proj/.git /pub/scm/proj.git 

As with the installation used, the following:

 ubuntu@site3-user03 :/$ sudo find / -type f -name known_hosts [sudo] password for ubuntu: ubuntu@site3-user03 :/$ 

Once in the past, I had a similar effect with another clone. At that time, he was cloned by a public repo for Linux for MSM SoC. However, at this point, the clone process also generated a message such as "unable to clone because it was not found on the remote." Forgot what ??? to read. Thus, in the final effect, I also had to manually check-out manually to clone the process. However, such a warning did not come in this case, unlocking the alsa-driver public repo.

Answer 1

I have never seen using the URL format that you use to clone the repository, since the standard should be: git://git.alsa-project.org:alsa-driver.git , in the format you use, you will clone the repository in naked mode, this similar to the --bare indication, which basically do:

Make a naked Git repository. That is, instead of creating <directory> and placing administrative files in <directory>/.git $GIT_DIR , make <directory> $GIT_DIR . This obviously implies -n because nowhere to check the working tree. Also, the branch heads on the remote control are copied directly to the corresponding local branch branches, without displaying them on refs/remotes/origin/ . When this option is used, neither configuration branches nor the associated configuration variables are created.

If you look at the project documentation that you are trying to clone, you will notice that to clone this particular project you must:

 git clone [e-mail] :alsa-driver.git alsa-driver cd alsa-driver git branch build remotes/origin/build git branch mirror remotes/origin/mirror git branch release remotes/origin/release