I'm trying to get a handle on a large repo (years old, 20k commits, >1GB), and I'm noticing weird behavior when I take shallow clones above a certain depth.
When I do `git clone --mirror --depth 10` or so, I get the expected behavior of a nice shallow copy. When I try a depth of around 40, I noticed it cloned 100 commits instead, and the disk-size approached half the size of the full repo. I know for certain there wasn't much large-file churn around the time, so this result is surprising. I was hoping for a more compact copy of 2 weeks of history. Is there a better way to achieve this? -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.