tree 9e2001084537775407d1e4376ec9a0f5791d32d6
parent a1985623415223662a51b240e814d5f22b231830
parent f937bc2f86ba2c2956b4228bd2386aaafc9afe83
author Junio C Hamano <gitster@pobox.com> 1557329843 +0900
committer Junio C Hamano <gitster@pobox.com> 1557329843 +0900

Merge branch 'km/empty-repo-is-still-a-repo'

Running "git add" on a repository created inside the current
repository is an explicit indication that the user wants to add it
as a submodule, but when the HEAD of the inner repository is on an
unborn branch, it cannot be added as a submodule.  Worse, the files
in its working tree can be added as if they are a part of the outer
repository, which is not what the user wants.  These problems are
being addressed.

* km/empty-repo-is-still-a-repo:
  add: error appropriately on repository with no commits
  dir: do not traverse repositories with no commits
  submodule: refuse to add repository with no commits