David Howells <dhowells@xxxxxxxxxx> writes: > to v2.6.29. I've attached the command output for reference. Version of git used, and the .git/config ([remote "origin"] section)? > warthog>git-pull > remote: Counting objects: 447, done. > remote: Compressing objects: 100% (57/57), done. > remote: Total 266 (delta 216), reused 254 (delta 207) > Receiving objects: 100% (266/266), 37.94 KiB, done. > Resolving deltas: 100% (216/216), completed with 105 local objects. > warning: no common commits > remote: Counting objects: 1075436, done. > remote: Compressing objects: 100% (176743/176743), done. > remote: Total 1075436 (delta 896164), reused 1072243 (delta 893708) > Receiving objects: 100% (1075436/1075436), 260.71 MiB | 307 KiB/s, done. > Resolving deltas: 100% (896164/896164), done. >>From git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6 This is intereseting because it shows that two separate transfer happened back to back, which I do not think is what recent git does. We used to first grab the objects reachable from primary refs (presumably [remote "origin"] fetch = refs/heads/*:refs/remotes/origin/*) and then turned around to ask for tags that possibly point at commits we freshly obtained during the first transfer (i.e. the ones reachable from the tip of "master"). In such an ancient version I vaguely recall some bugs fixed before we stopped doing this two-stage transfer altogether, but I do not recall offhand if a bug that loses track of what it just downloaded (which is what your description suggests) was among them. Rings a bell, anybody? -- 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
