git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Completion message for git-clone?

From
IDIan Dees <undees@gmail.com>
Date
Feb 8, 2008, 03:09 UTC
Message-ID
<ad4f9af90802071909s4dad180as26b2dd8b7600342f@mail.gmail.com>
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
Next: Jeff King
Message 1 of 4 in “Completion message for git-clone?”
  1. Ian DeesFeb 8, 2008
  2. Jeff KingFeb 8, 2008
  3. Jakub NarebskiFeb 8, 2008
  4. Ian DeesFeb 8, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.