This always perplexes me. I was cloning this
git clone https://android.googlesource.com/kernel/msm.git
And It seemed to be cloning resolving
Also, what happened on my system just now (windows 7). The automatic initialization (git init) did not take place during the
git clone URL
Operation. Also got the same succesful clone msg.
After I did a 'manual'
git init
The clone operation resulted in a dir with contents. After I repeated it.
So, just try a git init if a dir is empty after a git clone (and the master branch is not empty). Then repeat the clone.
After your first clone, if you have directories that are submodules of the parent repo, you need to initialize them with:
git submodule update --init
Using git submodule update --init --recursive
will also be needed if there are submodules inside submodules.
It seems that repository was cloned. Now you have to checkout something. What happens if you issue:
git branch
This particular git repository seems to not have any contents on its master
branch, which is the branch git checks out by default. It does however have another branch:
% git branch -a
* master
remotes/origin/HEAD -> origin/master
remotes/origin/android-msm-2.6.35
remotes/origin/master
So if you check out this branch:
% git checkout android-msm-2.6.35
Checking out files: 100% (33866/33866), done.
Branch android-msm-2.6.35 set up to track remote branch android-msm-2.6.35 from origin.
Switched to a new branch 'android-msm-2.6.35'
then there's also content in the working tree.