Re: Shallow clone

On 11/9/06, Junio C Hamano [off-list ref] wrote:

"Aneesh Kumar K.V" [off-list ref] writes:

quoted

But it seems to need some more work.  I just tried to clone
git.git with --depth=1 and it cauterizes each branch with two
commits (I think that is what depth=1 means -- the latest and
one behind it), but it pulled almost the whole repository
anyway, and it turns out that "git log v1.4.3-rc1" gives me the
full history leading to it.

Subsequent "git fetch --depth 99999" makes the branches
connected to the root commit, and I am reasonably sure we do not
have that many commits, but .git/shallow did not become empty.

I tried a local clone with --depth 2 and it showed two commits
in all the branches/DAG. But then doing a  pull --depth 4 listed more
commits than 4. I didn't look much into this.