Hi, all. Upon cloning a repository, the initial message reads: Initialized empty Git repository in path/to/new-repo/.git 0 blocks I'd wager "empty" means, "empty because Git is about to populate it." Even so, this wording could be a bit surprising to new adopters, especially coupled with the "0 blocks" suffix (is it really creating hardlinks on NTFS?). The impression is that the clone didn't work. The impression is, of course, eventually dispelled by looking inside the new directory. Is there a way to clarify the overall status of the clone operation? One other minor thing I noticed while futzing with clones: if you try to clone an empty repository, you get the same "Initialized empty repository" message, even though no such second directory is created. I'm not suggesting Git should suddenly start allowing empty cloning, but perhaps a "Empty repository; skipping clone" message would be helpful. --Ian - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
