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

Bug in shallow clone?

From
TKThomas Kieffer <thomaskieffer@web.de>
Date
May 28, 2014, 14:02 UTC
Message-ID
<5385EC5B.8050400@web.de>
Hi there Git developers,
I'm not sure if I found a bug in the command
git clone repo.git cloned_repo --depth 1
I follow these steps:

git init echo "First commit" >> test.txt git add -A git commit -am "First commit"

echo "Second commit" >> test.txt git commit -am "Second commit"

echo "Third commit" >> test.txt git commit -am "Third commit"

git clone --bare . ./bare.git
I then clone the bare repository with --depth 1.
git clone file:///path/to/bare.git ./clone --depth 1

It always returns the last two commits. If I specify --depth 2 it returns the last 3 commits.

If I use --depth 1 on a Github repository it works as expected.
Am I doing something wrong or is it really a bug?
Kind Regards,
Thomas Kieffer
BTW.: Git is amazing and I love it :)
Next: Duy Nguyen
Message 1 of 3 in “Bug in shallow clone?”
  1. Thomas KiefferMay 28, 2014
  2. Duy NguyenMay 28, 2014
  3. Dennis KaarsemakerMay 28, 2014

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.